How Pega Blueprint Changes Who Builds Software

Interested in being a guest? Email us at [email protected] is cranking out more code than ever, but that doesn’t mean teams are shipping the right outcomes. From PegaWorld, I sat down with Steph Lewis, Senior Director of Community Developer Programs at Pega Systems, to unpack what’s actually changing for developers, architects, and business stakeholders as AI, agents, and LLMs reshape enterprise delivery. We get specific about the Solution Designer role Steph helped build and why it’s showing up now. We talk about Pega Blueprint as a practical way to turn business ideas into a live application earlier, and how that changes the skills teams need across low-code development, workflow automation, and digital transformation. Steph explains why the goal never changes (delivering value), but the day-to-day work does, especially as “hands-on keyboard” tasks shrink and the need to challenge AI outputs grows. A big thread is the human edge: judgment, creativity, and the discipline to align what you build with what stakeholders truly need. We dig into the skills gap Steph sees most often, why workshops and real conversations beat passive training, and what sits behind eye-catching outcomes like 80% of projects going live in 90 days. We also zoom out to what Steph wants for the developer community over the next year: guiding architecture decisions, placing Pega in the right spots, and incorporating other agents only when it makes sense. If you care about modern software delivery, developer enablement, and the real-world impact of AI on building systems, this one’s for you. Subscribe, share this with a teammate, and leave a review with your take: what “human skill” will matter most as AI becomes default?Support the showMore at https://linktr.ee/EvanKirstel