INFLECT

Why it exists

Most AI-readiness conversations stop at tools. Teams trial Figma AI, an LLM-based summariser, or a coding copilot, and move on. That treats AI as an efficiency layer. INFLECT was built on the bet that AI is a different kind of moment: an inflection point that redefines what value looks like, not just how fast it gets produced. Efficiency is a feature; transformation is the strategy. The framework gives a design team a structured way to lead their organization through that transition rather than absorb it reactively.

The seven moves

INFLECT is an acronym, and each letter is a workshop move with its own activity and artefact:

1. Interpret the inflection. Surface mental models, biases, and assumptions about creativity, UX work, and AI. Teams reflect on past creative blockages, identify enablers, and name limiting beliefs they will need to release.
2. Navigate the narrative. Map the UX-AI system. Teams draw their current UX workflow, annotate tools and pain points, then overlay AI opportunities (green) and threats (red). The output is a literal picture of where AI helps, where it harms, and where the team is currently blind.
3. Frame the future roles. A “day in the life” exercise. Small teams sketch a desirable, realistic AI-enhanced future for a UX persona, then share. The point is to get specific about what the role looks like, not whether AI is a threat in the abstract.
4. Lead with learning. Define the wedge: a narrow, high-leverage starting point for AI adoption. Teams brainstorm options, score them on impact, feasibility, and momentum, and pick one to try.
5. Establish new rituals. Build the commitment loop. Each team writes a one or two sentence experiment statement, assigns an owner, and defines a timeline and feedback cadence. The wedge becomes a ritual, not a discussion.
6. Connect across functions. Design a learning loop. Teams write an if-then-because hypothesis, define one to three success metrics, and plan how they will reflect on the result with Product and Engineering partners.
7. Transform the system. Name the shift. Individuals reflect on personal growth; teams synthesise mindset shifts and declare what they will protect, release, or amplify.

The moves are sequenced deliberately. Skipping interpretation and going straight to wedges is the most common failure mode in AI rollouts; it produces tool adoption without the corresponding identity shift, and teams revert.

Ladders of Value

The companion tool inside INFLECT. Ladders of Value maps work along a spectrum from highly automatable to uniquely human. The ladder reframes “what is AI taking from designers” as “what work has the most leverage when humans focus on it.”

The high-leverage rungs in the workshop:

• Ethical and emotional literacy: judgement, empathy, accessibility advocacy.
• Problem framing and synthesis: defining what is worth solving and turning research into actionable insight.
• Cross-functional orchestration: trust, influence, and decision facilitation across Product, Engineering, and the business.
• Cultural stewardship: deciding what we protect about how we work as the tools change.

The lower rungs are deliberately not framed as “below” the designer. They are work that AI now does well, and the framework is explicit about handing it off. The shift the ladder names is from execution to orchestration.

The diagnostic

INFLECT also ships a ten-question leadership diagnostic that scores an organization on a 1-5 scale across vision clarity, strategic framing, investment, learning culture, role evolution, cross-functional alignment, ethical stewardship, emotional climate, communication depth, and system awareness. The output bands are:

• 40 to 50: Proactive transformers. Leadership is sensing the landscape and shaping it.
• 30 to 39: Aware but under-leveraged. Vision is emerging; investment and coordination are lagging.
• 20 to 29: Tactical adopters. Isolated tools are in use; strategy and culture are not aligned.
• 10 to 19: Legacy thinkers. AI is treated as a trend or threat rather than a transformation.

The diagnostic is the artefact most useful in leadership conversations. Naming a band tends to accelerate strategic decisions that abstract talk about AI never does.

How I use it

INFLECT runs as a single workshop (around three hours) or a two-part series: INFLECT Thinking (moves 1 to 3) and INFLECT Doing (moves 4 to 7). The thinking half is the more important half. Most teams want to skip ahead to wedges and rituals; the discipline of holding interpretation, mapping, and future-role framing first is what makes the rest of the framework actually change behaviour.

What stuck after the first run with my team: the language. Months after the workshops, “the wedge”, “ladders of value”, and “from execution to orchestration” were still showing up in design reviews and roadmap conversations. The framework’s value as a leadership artefact is partly the moves themselves and partly the shared vocabulary they leave behind.

Reflection

The piece I would change if I were running it again is the diagnostic. Scoring an organization in a workshop setting is useful for individual reflection but creates noise when you average across the room. I would now run it as a leader-only artefact, then bring the band score into the workshop as context, rather than asking participants to score live.

The piece I would not change is the bet at the centre of the framework: treat AI as an inflection point, not a productivity tool. Every team I have run this with arrives expecting tactics and leaves with a different conversation.