At Appian World 2025, something unexpected happened: I got publicly recognized as the #1 contributor to the Appian Community.

Now, if you’ve ever listened to the Appian Rocks Podcast, you know I don’t usually make a big fuss about awards or shiny things. I’d rather talk about how to fix your broken task reports or why your interfaces feel like a maze. But this one hit differently.

The Why Behind the Work

Most of what I do in the community—whether it’s blog posts like this one, code reviews, podcast episodes, or wild rants about dynamic interfaces—is because I enjoy it. I love seeing the “aha!” moment when a fellow developer realizes a better way to model a process or simplify an interface. I love being part of a community that builds real stuff with real impact.

So when Appian decided to highlight that effort, it wasn’t just a nod to me. It felt like recognition for how we build things, and why it matters.

What Recognition Really Means

For me, this isn’t about a title or a badge—it’s a reminder that sharing knowledge is part of the job. That creating clarity out of Appian chaos (and yes, there is chaos) helps not just one team, but dozens. And that even niche posts about process reports or the horrors of duplicated expressions have a place.

It also means more visibility, more questions, more collaboration—and hopefully, more opportunities to raise the bar for everyone building with Appian.

What’s Next?

Simple: keep going. I’ll continue doing reviews, building better tools, and challenging assumptions. And yes, I’ll write about it, and probably record another podcast episode where I complain about tasks without deadlines. 🙃

To the Appian Community: Thank you! This is yours as much as mine.

Rock it!