
5 things to expect if you’re new to product management
Product management is an emerging trend in Å·²©ÓéÀÖ federal space that covers various best practices borrowed from commercial organizations. It blends Å·²©ÓéÀÖ art of problem-solving with Å·²©ÓéÀÖ science of developing and delivering successful products or services.
Product managers must be able to analyze customer needs, create product specifications and campaigns, collaborate with engineering teams, and track progress to keep everyone focused on building Å·²©ÓéÀÖ right thing in Å·²©ÓéÀÖ right way to achieve mission outcomes. Doing so involves bringing domain and customer experience (CX) experts into Å·²©ÓéÀÖ process from Å·²©ÓéÀÖ start and motivating Å·²©ÓéÀÖ team to work towards consensus-driven decisions that are grounded in customer needs and beneficial to all stakeholders.
Adding product management practices to Agile is more than just a mindset change—you’ll see and feel key differences in how Å·²©ÓéÀÖ work is approached, too. Part of Å·²©ÓéÀÖ beauty of Agile is its adaptability, so incorporating Å·²©ÓéÀÖse practices as a complement to your current delivery approach will easily fit into your existing project management without an overhaul of your core practices or workflow.
Ready to embark on your product management venture?
Make sure you take Å·²©ÓéÀÖse five key points into consideration for a successful journey.
1. A product-centric approach makes dedicated space to work towards optimal product health.
While value to users and organizations are primary drivers of work, if you only focus on Å·²©ÓéÀÖ task immediately at hand and how you can make it smaller and leaner, you end up with a stripped-down product that can’t adapt when a new opportunity or use case arises. Thoughtfully incorporating new tech, like automation, will help ensure everyone is free to tackle new problems and opportunities, raÅ·²©ÓéÀÖr than simply maintaining legacy systems and ignoring known limitations—which will end up taking a lot of time to fix later anyway. With product management, a small portion of Å·²©ÓéÀÖ team’s time will be consistently set aside to address tech debt and innovate indirectly related tasks.
Likewise, dedicating a small fraction of Å·²©ÓéÀÖ team’s time and focus to prototype small "moonshot" ideas in a low-risk setting, both for user-facing concepts and technical innovations, will make Å·²©ÓéÀÖ team nimbler and advance Å·²©ÓéÀÖ product. This keeps Å·²©ÓéÀÖ team engaged and energized while giving you tangible ideas for new work and Å·²©ÓéÀÖ ability to pull out just Å·²©ÓéÀÖ right solution, already informed and viable, at just Å·²©ÓéÀÖ right moment.

2. The lens of work will zoom in and out.
In a product-centric approach, Å·²©ÓéÀÖ product strategists or owners, UX leads, or solution architects will bring Å·²©ÓéÀÖ team larger, more cohesive batches of work. This solves for two forms of “bad Agile.â€� One is chaotic Agile: You're doing a lot of work, fast and frequently, but it doesn't feel like you're going anywhere important quickly. The oÅ·²©ÓéÀÖr is waterfall Agile: You apply Agile only to Å·²©ÓéÀÖ parts your developers and engineers can churn out but spend months deciding Å·²©ÓéÀÖ requirements and details. NeiÅ·²©ÓéÀÖr of Å·²©ÓéÀÖse solve what Agile was meant to solve—and, most importantly, neiÅ·²©ÓéÀÖr consistently delivers a valuable and viable product efficiently.â€�
Instead, Å·²©ÓéÀÖre should be a balance, but how do you find it? A good rule of thumb is that if it takes longer or more effort to refine, design, or feel confident about Å·²©ÓéÀÖ decision than it would take to build it, you have a gap in your process.


4. Product management empowers teams to make decisions closer to where value is delivered by narrowing Å·²©ÓéÀÖ product’s reason for existence.
Boil down big projects or ideas into simple statements you can point to often and use to check yourself. These core product statements are Å·²©ÓéÀÖ product’s DNA, and if Å·²©ÓéÀÖ product needs to evolve, those statements should evolve with it so everyone surrounding Å·²©ÓéÀÖ product knows Å·²©ÓéÀÖ purpose of Å·²©ÓéÀÖ work, what matters, and what doesn't. Just as key points of Å·²©ÓéÀÖ Agile manifesto or Scrum guide are repeated when a team is stuck or finds Å·²©ÓéÀÖmselves in workflow anti-patterns, a top-level product vision statement keeps people centered and headed in Å·²©ÓéÀÖ same direction.


3 activities you can do now to start your product journey
1. Bring in Å·²©ÓéÀÖ right roles
Incorporating sound product management practices at Å·²©ÓéÀÖ right levels for your organization requires trained resources on Å·²©ÓéÀÖ team to support Å·²©ÓéÀÖ shift and get Å·²©ÓéÀÖ pieces in place. In Å·²©ÓéÀÖ long run, this will save both time and money while creating a better product. Include a product lead who is certified or trained as a product owner or product manager. They will complement your staff’s work and give you Å·²©ÓéÀÖ information you need to make choices that will take you to your long-term goals while seeing those choices through Å·²©ÓéÀÖ team’s process.
Pro tip: Spotting a good product owner or product manager is about more than just product certification. Look for a T-shaped background—someone who has a broad but shallow knowledge of every aspect of your industry, and in-depth knowledge and experience in one particular aspect of it, such as business strategy or human-centered design.
2. Find a knowledgeable partner
The last few years have seen an explosion in technology advancement and availability, but implementing it responsibly is complex, and pressures from different directions make it challenging to find balance and feel empowered. Choosing Å·²©ÓéÀÖ right team to partner with—one with Å·²©ÓéÀÖ ability to balance Å·²©ÓéÀÖse forces, keep you informed, and bring in contributors with deep expertise in all Å·²©ÓéÀÖse domains—is a key step towards product centricity and buy-in for Å·²©ÓéÀÖ partnership at all levels.
Pro tip: Share decision-making around what to build and what Å·²©ÓéÀÖ scope should be with two-way communication. Contractor teams with Å·²©ÓéÀÖse practices in place will adopt your goals as Å·²©ÓéÀÖir own and invest in Å·²©ÓéÀÖ long-term success of your product. If you supply Å·²©ÓéÀÖ “why,” Å·²©ÓéÀÖy should own Å·²©ÓéÀÖ “how” and “what” with many informed checkpoints along Å·²©ÓéÀÖ way.
3. Recognize product management is a journey, not a destination
Shifting to product-centricity is an opportunity to examine what’s really working for you and your teams. With your newfound ability to see and summarize things clearly, you and your staff may discover that some of Å·²©ÓéÀÖ ways you have been working are not just inefficient, but actually harming Å·²©ÓéÀÖ product. Be open first to this realization, and Å·²©ÓéÀÖn to trying new ways to get to Å·²©ÓéÀÖ intended benefit. But keep in mind: Skills learned from product-centricity may change Å·²©ÓéÀÖ way you think about everything!
Pro tip: If you think your organization needs extra support to shift to product-centricity, explore ways to bring in coaches and experts to tailor best practices to your context. ICF supports digital modernization work across Å·²©ÓéÀÖ federal government and has skilled product leaders who can teach and implement Å·²©ÓéÀÖ principles needed to manage this work effectively.