tech·nic·al·ly agile

Does Your Team Truly Understand Your Product Vision and Goals?

Unlock your team’s potential! Discover how a shared product vision drives Agile success and empowers decision-making in this insightful video. 🚀

Published on
6 minute read
Image
https://nkdagility.com/resources/CPYTApf0Ibs

When it comes to Agile transformation, one of the most crucial aspects often overlooked is the shared understanding of the product vision and strategic goals within the team. It’s not enough to have a beautifully crafted vision statement or a set of strategic goals pinned to the office wall; every team member needs to internalize these concepts and understand how their daily work contributes to achieving them. This understanding forms the foundation of true agility within an organization.

The Second Agile Litmus Test: Is Your Product Vision Truly Understood?

The second question that we should be asking leadership in any Agile organization is simple yet profound: Is there a product vision that lays out the strategic goals, and do all members of the team understand both of those things? More importantly, are they able to see how their everyday work contributes to these overarching objectives?

In my experience working with various organizations, this understanding is often lacking. Surprisingly, even in companies that have a clear product vision and strategic goals, these are not always effectively communicated to the people actually doing the work. This disconnect can be more detrimental than the absence of a usable working product.

The Test: Do Your Team Members Know the Vision?

Here’s a straightforward test: go to any team member in your organization and ask them:

  • What is the strategic goal of our business?

  • What is the vision for our product?

  • How does your daily work contribute to these goals?

If they can’t articulate these clearly, then the vision doesn’t truly exist in your organization. It might be on paper, but if people haven’t internalized it, it’s as good as non-existent.

💡 Pro Tip: Regularly check in with your teams to ensure they not only know the vision but also understand how their work aligns with it. This practice can uncover gaps in communication and alignment early on.

Why Shared Understanding is Crucial

Shared understanding isn’t just about everyone being on the same page; it’s about enabling better decision-making, fostering collaboration, and maximizing the value created for your customers.

The Impact on Decision-Making

Consider the countless micro-decisions your team members make every day. Whether it’s a software engineer deciding on an architecture, a marketer crafting a campaign, or a tester planning their approach—these decisions are made within the context of what they understand about the product vision and goals.

However, if this context isn’t clear or fully understood, the decisions they make might not align with the broader objectives. This misalignment can lead to:

  • Wasted efforts on tasks that don’t contribute to the overall goals.

  • Decisions that conflict with the product’s strategic direction.

  • A decrease in the overall value delivered to customers.

By ensuring that every team member understands the product vision and strategic goals, you empower them to make better decisions—decisions that are more likely to move the needle in the right direction.

Collaboration and Value Creation

When team members understand the vision and goals, they are more likely to collaborate effectively. They know why they’re doing what they’re doing and can see how their work fits into the bigger picture. This clarity fosters camaraderie and a sense of shared purpose, which are essential for any high-performing Agile team.

On the flip side, when this understanding is absent, teams may start to work in silos, pulling the organization in different directions. This disjointed effort can lead to wasted resources and a significant reduction in the value delivered to customers.

💡 Pro Tip: Foster a culture where the product vision and goals are regularly communicated and discussed. Use tools like interactive whiteboards or team workshops to visualize how different tasks contribute to the overall strategy.

The Importance of Communicating Vision and Goals

So, how can you ensure that your team is aligned with the product vision and strategic goals? Here are some practical strategies:

1. Regular Communication

  • Vision Workshops: Hold regular workshops where the product vision and strategic goals are discussed in detail. Encourage team members to ask questions and express their understanding of these concepts.

  • Daily Stand-Ups: Use daily stand-ups to remind the team of how their current tasks align with the product vision and goals.

2. Visual Reminders

  • Visual Roadmaps: Create visual roadmaps that clearly outline the product vision, strategic goals, and how various tasks and projects contribute to these. Place these roadmaps in visible areas in your workspace.

  • Digital Dashboards: Utilize digital tools and dashboards that update in real-time to show progress towards strategic goals, helping teams stay aligned.

3. Leadership Involvement

  • Leadership Q&A Sessions: Encourage leaders to engage with teams regularly, answering questions and providing clarity on how their work fits into the broader picture.

  • Feedback Loops: Establish feedback loops where team members can voice their understanding (or lack thereof) of the product vision and goals, allowing leadership to address any gaps.

The Agile Litmus Test: Are You Truly Agile?

The concept of an Agile Litmus Test, as dreamed up by the US Department of Defense, serves as a valuable tool for self-reflection within your organization. It’s not about checking boxes or adhering to a rigid set of rules; it’s about genuinely assessing whether your practices align with Agile principles.

The Six Questions

To truly gauge your organization’s agility, consider the following six questions:

  1. Is there a clear product vision and strategic goals?

  2. Do all team members understand these goals?

  3. Can they articulate how their work contributes to these goals?

  4. Is there a culture of continuous improvement?

  5. Do teams collaborate effectively towards common objectives?

  6. Are decisions made at every level aligned with the strategic goals?

If the answer to any of these questions is “no,” then your organization might still be working towards true agility. And that’s okay. The key is to acknowledge where you are and make concerted efforts to bridge the gaps.

💡 Pro Tip: Use these questions as a regular check-in during retrospectives to assess your team’s alignment with Agile principles and make adjustments as needed.

Conclusion: Aligning Vision, Goals, and Daily Work

In the end, Agile isn’t just a set of practices or a methodology—it’s a mindset. And central to this mindset is the alignment of vision, goals, and daily work. By ensuring that every team member understands and internalizes the product vision and strategic goals, you set the stage for better decision-making, stronger collaboration, and ultimately, greater value creation for your customers.

Remember, it’s not just about having a vision—it’s about living it every day, in every decision, and in every action your team takes. That’s the true essence of agility. 🚀 Take Action: Start today by asking your team the tough questions. Do they know the vision? Do they understand the goals? And do they see how their work contributes to the bigger picture? If not, it’s time to bridge that gap and unlock the full potential of Agile within your organization.

The second question that we should be asking leadership of organisations is, is there a product vision that lays out the strategic goals? And do all members of the team, all people doing work inside of our organisation, understand both of those things? And are they able to see how the work they do every day contributes to both of them? This is really lacking in organisations. It’s probably more lacking than creating usable working product. Most organisations that I’ve worked with, even if they do have a clear product vision for their product and strategic goals for their business, it’s not well communicated to the people in the organisation.

A key test for this is to go to folks in your organisation and ask them what the strategic goal is, what’s the vision for the product, what are the strategic goals for the business, what’s the strategic goals for the product? And if they aren’t able to articulate it, then it doesn’t exist in your organisation. It might exist on paper, but if people aren’t able to internalise it and articulate it, then they don’t understand it and it’s not there.

The second part of that is even more powerful, and that’s that the people doing the work need to understand how the things that they’re doing every day contribute to those overall vision and goals. Because the doers in your organisation and management and everybody in your organisation are making lots of little micro decisions within the context that they understand of what it is we’re trying to do. They’re going to make continuous micro decisions. Software engineers are going to make decisions about what architecture to choose, about ways to build things, and they might talk to each other or they might talk to nobody when they make that little decision. Because it’s a little micro decision, in order to get somebody to help you with that decision, you need to impart the context.

Quite often, other people don’t understand the context because what you’re talking about is incredibly technical. It could be coding technical, it could be testing technical, it could be marketing technical. They can’t just go ask a boss, ask a leader, ask somebody senior in the organisation because they don’t understand the context. The only way to enable those people, because they’re going to make the decision anyway, is for them to understand what it is you’re trying to achieve, where it is we’re going as a business, what are we trying to do with our product, where do we think it’s going. That will enable them to make more of the right decisions and less of the wrong ones.

This is how we maximise the amount of work not done, how we maximise the value that we deliver to our customers. Because the people that are doing the work, if they’re not connected to that goal and vision and what it is we’re trying to achieve, how do they value what it is they’re doing? Are they just turning up for their day job and they’re punching, you know, like a machine punching cards? At the end of your day, do you go home? Or do you feel for the customer? Do you understand the wants and needs for the customer of the business, of what it is we’re trying to achieve?

Part of that is creating camaraderie, creating this story of, are we as a group all working together towards a common goal? Or are we potentially working against each other because we all have our own idea of what our common goal and vision is, and we’re all doing our own thing and perhaps pulling each other in different directions within our business? So do you have that alignment so that we can share knowledge, share decisions, so that even decisions that we make on our own are working towards a common outcome? That’s the very definition of team, right? A group of people working together towards a common goal.

So you need to have clear product vision and strategic goals, and you need to ensure that everybody that’s working on your product understands the vision and the strategic goals, and also how the work that they’re doing every day contributes to that. So how can you help them make those connections? If your answer to any one of these questions, or the answer of your business to any one of these questions, is no, we’re not doing that, then you would probably, I probably wouldn’t consider that you’re already in the agile space, right? You’re not already agile. You might be working towards it, and you might have put in loads of effort, but unless you can mark every single one of these six questions as yes, we do this, this is how things work here, then we’re still lacking. We’re still trying. We’re still working towards being agile.

Now, this is just a litmus test dreamed up by the US Department of Defense, but they are probably the least likely place for you to expect something with this high a bar to have come from. I’m not going to go into a team and work with a team or a company, and if they’re not doing these things, then I’m going to say, well, you guys suck, you’re not agile because you’re not doing this. That’s not how we work towards success. But I think it’s hugely valuable from the perspective of self-reflection for you all to think about the processes and practices in your organisation and how many of these six questions you are able to achieve, and what could you do to make it a little bit easier for the teams, for the people doing the work to work towards this idea of not being agile BS.

Agile Values and Principles Agile Planning Common Goals People and Process Strategic Goals Agile Leadership Organisational Culture Software Development Team Motivation Agile Project Management
Comments

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

Microsoft Logo
Capita Secure Information Solutions Ltd Logo
Graham & Brown Logo
DFDS Logo
Slaughter and May Logo
Emerson Process Management Logo
Hubtel Ghana Logo
YearUp.org Logo
Freadom Logo
Trayport Logo
Slicedbread Logo
Higher Education Statistics Agency Logo
Bistech Logo
Teleplan Logo
Milliman Logo

NIT A/S

Deliotte Logo
Sage Logo
Washington Department of Enterprise Services Logo
Royal Air Force Logo
Ghana Police Service Logo
Washington Department of Transport Logo
Nottingham County Council Logo
New Hampshire Supreme Court Logo
Boeing Logo
Akaditi Logo
Genus Breeding Ltd Logo

NIT A/S

YearUp.org Logo
Healthgrades Logo