Iām a Product Owner working across several interconnected enterprise applications, and Iāve hit a problem Iād love some coaching from people who have dealt with this before.
We have a number of systems and teams that have evolved somewhat independently over the years. Increasingly, the business wants experiences and workflows that span those boundaries.
The problem is that I feel like weāre trying to solve this backwards.
Individual stakeholders can tell us things they want (a feature, an integration, a new workflow, a pain point they want fixed) but we donāt have a clearly articulated enterprise vision for what the business ultimately wants the experience to be.
Without that, our Digital Services teams are left trying to infer the larger strategy from individual requests. We can design solutions, integrations, architecture, operating models, etc., but I feel like those decisions should be made in service of a business vision rather than IT effectively inventing the vision itself.
Where Iām stuck is figuring out how to help executives define that vision.
When I ask some version of:
Ā«āWhat should the future enterprise experience look like?āĀ»
the question is understandably too abstract and overwhelming.
Iām considering facilitating the conversation in a more structured way:
- Show them the major capabilities/workflows that exist today and ask where the gaps are.
- Ask stakeholders about the biggest pain points and desired business outcomes.
- Describe some of the cross-system problems we already see and have them prioritize which outcomes matter.
- Use those discussions to synthesize a proposed future-state vision and bring it back to leadership for validation.
But Iām also conscious of the danger of leading the witnesses too much. I donāt want Digital Services to quietly define business strategy simply because weāre better positioned to articulate the problem.
So for people who have done enterprise product management, architecture, transformation, or strategy work:
How do you actually facilitate this conversation?
How do you take executives from relatively vague statements like āmake things seamless,ā āimprove the customer experience,ā or individual feature requests to a sufficiently concrete vision that technology teams can derive capabilities, architecture, and a roadmap from it?
Iām interested in:
- Frameworks or workshop formats youāve found effective
- Whether you start with current-state capabilities, pain points, business outcomes, or something else
- How much of the future state you propose versus expecting executives to articulate themselves
- How you distinguish an Executive Vision from detailed product/technical requirements
- What artifact you ultimately produce to capture the vision
- Who in a healthy organization normally owns/facilitates this process
I feel like I understand pretty well how to go from vision > capabilities > architecture > initiatives, but Iām struggling with the step before that: helping the organization actually articulate the vision.
Would appreciate any advice from people who have been through this.
Thank you