UX strategy for in-house teams.
A two-day in-house programme, or four half-days, on getting an organisation to act on the design and research work it already has the skill to produce.
Built for teams who can do the work, but can't get it acted on.
This isn't a research skills refresher. It assumes your team can already do the work, and is about why the organisation around it doesn't act.
- •UX and product leads who can do the work but can't get the organisation to act on it.
- •Design teams whose research gets collected and then ignored.
- •Teams measured on output rather than outcome, and looking to change that.
- •Anyone trying to build a UX practice inside an organisation that doesn't yet see it as strategic.
Six things you have to get right.
Run against your own product and organisation, not a hypothetical one.
Why UX is a strategic choice, not a delivery function
Where the evidence for design-led performance is strong, and where the strategic argument gets overstated.
→ the strategic case for UX, evidence-checkedModelling your experience over time
Use the Kano model to see which features are still differentiators, and which are now just expected.
→ a Kano map of your features todayDesign debt and experience rot
Name what accumulates when a product only ever gains features and never sheds any.
→ a design-debt list, with candidates to killWhere your organisation actually sits
Apply a maturity model to your own team and name the specific barrier in front of you.
→ your maturity baseline, mappedBuilding buy-in above and below
Build a different argument for leadership than for the champions alongside you, both backed by real data.
→ an internal narrative that landsMaking it stick
Wire falsifiable hypotheses and measurable outcomes into the process, so the change survives past the workshop.
→ an Experiment Canvas for a testable hypothesisWant a first read before you talk to us?
Try the free UX Maturity Health-Check: 8 questions, about 5 minutes, an instant and indicative read on where your team sits on the same maturity model this programme uses.
Try the free health-checkArtefacts, not just a good discussion.
- •A UX maturity assessment of your own team, with the specific barriers named.
- •A Kano-mapped view of where your product's features actually sit today.
- •A buy-in plan for at least one real initiative, aimed above and below you.
- •An Experiment Canvas for a hypothesis you can test on your own product.
There's also an open-enrolment version.
UX Strategy is one of our established courses. If you want to see the material before committing a whole team, or you only need to send one or two people, the open-enrolment course covers the same ground. See the UX Strategy course →
If the strategic question in front of your team is specifically about where agentic AI fits into your journeys, and when it should hand off to a human, see our agentic AI in-house programme. See a related engagement: GroupM.
Before you enquire.
Is this a research skills course?
No. It assumes your team can already do research and design work, and is about the organisation around that work: why decisions arrive with the solution already chosen, why evidence gets collected and ignored, and how to change that instead of producing more of it.
What's the Kano model and why does it matter here?
It's a way of modelling which features delight users, which are basic expectations, and which are neutral, and the fact that a feature moves between those categories over time. We use it to show why a roadmap built around yesterday's differentiators keeps under-delivering, and to prioritise what to build next.
Is this the same as the open-enrolment UX Strategy course?
It's the same subject taught the same way, but scoped and run for your team, against your own product and organisation, rather than a mixed group of individual learners. If you want to try the material first, or send one or two people rather than a whole team, see the open-enrolment version at /courses/ux-strategy/.
Can this be combined with other in-house training?
Yes. It's often run alongside our UX research day, or our complex journeys and service design day, since strategy, research and delivery are usually the same underlying problem. Tell us on the form below and we'll scope the days together.
What's UX maturity?
UX maturity describes how embedded user-centred design is in an organisation's decision-making, from teams where design is applied late and inconsistently to teams where it shapes strategy from the start. A UX maturity model is used to identify where a team sits now and what's specifically blocking it from moving further.
Enquire about this programme.
Tell us about your team, the organisation problem you're trying to solve, and your preferred timing. We'll get back to you within 2 business days.