Business Engagement
Teaching IT people to draw out demand, and translate it.
The skill that decides whether IT is a partner or a ticket queue.
Delivery. Scoped to a team, built on live demand from your own business.
IT teams, business analysts, architects and anyone who has to sit between a sponsor and a delivery plan.
Requirements arrive as solutions, projects get rebuilt after go-live, or the business has started going around IT entirely.
What we teach
Running the conversation
How to open a demand conversation, what to ask, and how to get past the solution someone arrived with to the problem underneath it.
Requirements from people who do not write them
Observation, examples, walkthroughs and the awkward-case question — techniques that work when nobody can tell you what they need in writing.
Translating both ways
Business language into something delivery can plan against, and technical constraint into something a sponsor can decide with.
Framing the problem
Process, data, capability or expectation — naming which one you are looking at before anything is scoped.
Challenging respectfully
How to say this is not worth doing yet, to someone senior, and keep the relationship.
Demand triage
Sizing, qualifying and routing a request so it reaches the portfolio in a shape that can be ranked.
Expectation management
Committing to what is real, saying no with a reason, and keeping a sponsor informed in a way that does not require a status report.
Practice on live demand
Sessions run on your own current requests, so the output is useful the week after.
Requirements arrive as solutions.
- 01The request
“We need a dashboard.” “We need Copilot.” A solution, with the problem left unstated.
- 02The problem
Reached by asking, observing and walking the work — without making anyone feel interrogated.
- 03The awkward cases
The exceptions people handle without noticing. Never in the document, usually what blows the estimate.
- 04Something plannable
Scoped, sized and routed to <a href="/services/technology-strategy-advisory/it-portfolio-management">the portfolio</a> in a shape that can be ranked.
A team that says yes to everything is a queue, not a partner. Saying this is not worth doing yet — with a reason and an alternative — is what gets IT into the conversation earlier next time.
We teach IT teams to run the demand conversation: getting past the solution someone arrived with, drawing requirements out of people who have never written any, surfacing the awkward cases, and routing work into the portfolio in a shape that can be ranked.
Requirements arrive as solutions
“We need a dashboard.” “We need Copilot.” Behind each one is a problem nobody has stated, and the job is to get to it without making the person feel interrogated. That is a teachable technique, not a personality trait.
The awkward case is where the work hides
Every process has exceptions people handle without noticing they are exceptions. They never appear in a requirements document, and they are usually what blows the estimate. Asking for them specifically is most of the craft.
Saying no is part of the service
A team that says yes to everything is not a partner, it is a queue. Being able to say this is not worth doing yet, with a reason and an alternative, is what gets IT invited to the conversation earlier next time.
What you keep
The code and the data·Your existing relationships·Approval and control·The ability to stop·The off switchWhat that means
Start with a 45-minute briefing.
No pitch. We’ll map your situation against what actually works and tell you honestly where to start.