Check out some of the various tools I bring to the organization and product delivery teams.
The most impactful thing companies can do for their product delivery squads is to equip them with the tools, methodologies, and autonomy needed to make informed decisions. By coaching teams on best practices and empowering them to take ownership of their decisions, organizations foster a culture of accountability, creativity, and efficiency. Here are a few key elements that squads **must** incorporate:
1. Workshops: Slowing down to speed up. Workshops are essential for engaging stakeholders early in the discovery and ideation phases, ensuring alignment and buy-in throughout the process.
2. Design Thinking: A critical methodology that every junior-to-mid-level product manager and designer should utilize, especially when navigating complex projects. It encourages a human-centered approach to problem-solving.
3. Decision-Making Tools: Utilizing tools like Opportunity Trees, Risk/Confidence Matrices, and Journey Maps helps squads visualize options, assess risks, and make data-driven decisions.
4. Qualitative Testing: Moderated and unmoderated user testing helps teams understand how users feel about their experience, offering invaluable insights into usability and satisfaction.
5. Quantitative Testing: Tools such as A/B testing and iterative testing allow teams to track behaviors, measure outcomes, and refine their approach based on data.
6. Best Practices: Teams should nurture curiosity, embrace storytelling, foster collaboration, and prioritize frequent alignment meetings. Every squad and individual operates differently, but success lies in moving forward with clear intent.
Researcher, Lauren standing proud in the completion of foundational research into user-personas.
Mapping our end-to-end user journey and aligning it with our JTBD product goals gave leaders clear visibility into potential gaps, overloaded teams, and neglected areas. This exercise not only enhanced ownership but also improved communication, providing teams with clarity on where to focus, addressing the confusion they often felt.
When building an outcomes flow chart, it’s important to first clearly define the end goals or desired outcomes for the product or initiative. This allows us to consider strategies that focus on measurable results, such as increased user engagement, revenue growth, or improved customer satisfaction. Break down each outcome into actionable steps, ensuring each step is supported by data and key performance indicators (KPIs).
A linear roadmap typically follows a straightforward, step-by-step progression of tasks and milestones. It focuses on delivering a predefined set of features or initiatives in a specific order, often tied to strict timelines.
In contrast, a strategic roadmap is more flexible and outcome-driven. Instead of focusing on a fixed sequence of tasks, it prioritizes goals and outcomes, allowing for adjustments based on evolving market conditions, user feedback, or internal learnings. Strategic roadmaps emphasize long-term vision and adaptability, encouraging teams to align their efforts with broader business objectives while remaining agile in their execution.
OKR (Objectives and Key Results) mapping aligns organizational goals with measurable outcomes, ensuring that every effort supports broader business objectives. By setting clear objectives and tracking key results, OKR mapping creates transparency and focus, keeping teams aligned and accountable.
The benefits are clear: OKR mapping provides clarity on priorities, fosters accountability, and promotes agility. It enables teams to adjust focus as needed and keeps progress measurable, driving continuous improvement and strategic alignment.
Why is this problematic?
At this level, the design manager should understand how and when to diverge and converge in collaboration. Hesitation to move forward without external input stifles innovation, slows production, and diminishes the design team's leadership role in the discovery process. We know squads encounter a slew of touch-points per project, the goal of the leader should be to reduce as many steps as possible while maintaining quality delivery.
Why is this a red flag?
A designer at this level should be confident in making smaller decisions independently. If a senior leader is too involved in these low-impact tasks, it signals a lack of trust in the team’s capabilities. This not only slows down production but also hinders the designer's professional growth by keeping them overly dependent on upper management. Leaders need to be clear on the appropriate work for approvals and the type of work to just do it.
Why is this an issue?
This situation exemplifies an organization, albeit with good intentions, overextending processes that burden squads with administrative tasks outside of their core responsibilities. Headcount justification and resource management fall within leadership's purview, not the squads’. The more time squads spend on nonessential tasks, the less time they can dedicate to their primary focus: delivering high-quality products.
JJ Riggs Portfolio | Director, Product Design
Salt Lake City, Utah, United States
Copyright © 2025 JJ Riggs Portfolio - All Rights Reserved.
Powered by GoDaddy
We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.