The Landing Method

Beyond general consulting, we also work with a structured methodology we call the Landing Method. It focuses on the point where even well-designed initiatives can struggle: adoption.

Two initiatives. Same competent design. Opposite outcomes

The Landing Method came out of watching, up close, why well-designed initiatives get stuck and what changes when someone treats adoption as part of the project, not as an afterthought.

Got stuck

A capacity tool nobody used

Well built and well introduced, but tooling friction and the wrong incentives made the communication irrelevant. The team was back on spreadsheets within weeks.

Took hold

A post-reorg system that stuck

Same level of complexity, but with active friction removal and co-design with the people who'd actually use it. It became part of the workflow, not a parallel system.

Six stages, from framing to sustaining

Each stage deals with a specific way adoption fails, not with the design of the initiative itself.

  1. 01

    Frame

    Define what's actually at stake, for whom, and why now.

  2. 02

    Friction

    Map where adoption is likely to get stuck before it does.

  3. 03

    Pilot Gate

    Test at small scale before committing the whole team.

  4. 04

    Equip

    Give people what they were missing to adopt without extra effort.

  5. 05

    Instrument

    Measure real adoption, not just the initial rollout.

  6. 06

    Sustain

    Keep the gain after the project's attention has moved on.

The Landing Method

The fastest way to know, with evidence, where your initiative is likely to get stuck.

Fixed scope · 2 weeks

Adoption friction diagnostic

A direct diagnostic of an initiative already underway: where the friction is (or will be), and what to do about it before it becomes an expensive problem to fix.

Friction mapNet-friction estimateAdoption scorecardPrioritized readout

Investment set in conversation, based on scope and context.

Talk about the Landing Method →