Why UX Needed to Be There
This particular PI included multiple features that would require UX design throughout the quarter. Being present meant I could hear directly from Product about requirements, learn about technical constraints from Development, and get clarity on priorities early. That alignment is invaluable. It ensures that the experiences we design are not only intuitive for users but also realistic for the teams executing the work.
Choosing a Service Design Blueprint
The install workflow wasn’t just about screens or UI. It involved other systems, hardware, installation steps, and human touchpoints long before a user even opened the application. A Service Design Blueprint was the best tool to visualize that complexity. It gave the team a shared map of what happens before, during, and after installation. Seeing the full picture helped everyone understand how the application fits into a larger ecosystem that depends on both technology and people.
Bringing Everyone Into the Process
The session brought together Development, Product, UX, and Client stakeholders. The collaboration was energizing. Each perspective added another layer to the blueprint, and the conversation became richer as everyone recognized how their work connected. By the end, the team was so proud of what we created together that they posed for photos in front of the finished blueprint. It was a small moment, but one that perfectly captured the sense of shared accomplishment.
What We Learned Along the Way
Mapping out the full journey revealed gaps in the workflow that weren’t obvious before. It also confirmed the areas where we had a solid understanding of the process and exposed dependencies across systems and technologies. One of the most eye-opening insights was how much time and effort the pre-installation tasks required—long before the application even came into play. The blueprint gave us clarity on what work still needed to be done and what improvements could make the experience smoother end-to-end.
Leadership Takes Notice
One of the client stakeholders shared the blueprint with company leadership as a quarterly highlight. That recognition was incredibly rewarding and also opened the door for new conversations. Leadership wanted to explore how UX could help map and design the pre-planning phase as well. What started as a PI Planning activity ultimately expanded into a broader opportunity to shape more of the customer journey.
Advice for UX Professionals New to PI Planning
For UX practitioners stepping into PI Planning for the first time, preparation and presence go a long way. Connect with team leads ahead of time so you understand the agenda and what topics may need design support. Come prepared with potential solutions or early concepts—not because they need to be final, but because they spark meaningful discussion. And don’t be afraid to advocate for bringing UX activities into the sessions. Without intentional design conversations, PI Planning can easily lean too heavily toward technical decisions.
If your team is looking to bring more clarity, alignment, and user-centered thinking into PI Planning, Improving can help. Our UX and facilitation experts partner with organizations to introduce tools like Service Design Blueprints, journey maps, and collaborative planning practices that strengthen cross-functional understanding and lead to better outcomes. If you’re ready to elevate your next PI Planning session, connect with us today.
