Running a Katmai Pilot

How teams evaluate Katmai deliberately and roll it out with confidence.

Not every team needs a formal pilot.

But for teams that do, a pilot should test how work changes, not just whether features function.

This guide shows how to run a focused Katmai pilot that produces clear signals and confident decisions.

What a Katmai Pilot Is (and Isn’t)

A Katmai pilot is meant to test:

• How your team communicates day to day
• Whether work moves faster with shared presence
• If spontaneous interaction replaces scheduling

It is not meant to:

• Replicate your existing meeting load
• Evaluate Katmai as “Zoom in 3D”
• Measure success by raw usage alone

You’re testing a way of working, not a checklist.

Who Should Be Included

Choose a group that:

• Collaborates frequently
• Spans roles or functions
• Includes at least one visible leader

Avoid pilots made up only of passive participants.

Katmai works when people actively show up.

How Long a Pilot Should Run

A meaningful pilot usually needs 2 to 4 weeks.

Shorter pilots often fail because:

• Teams don’t change habits fast enough
• People default back to calendars and links
• Presence hasn’t had time to compound

Behavior change takes time.

Set Expectations Up Front

Before the pilot starts, tell participants:

• When you need to talk or meet, go to the office
• Avoid sending internal meeting links
• Spend time in the office, even when not meeting
• Use presence before messages

Clarity up front prevents confusion later.

How to Run the Pilot Day to Day

Encourage the team to:

• Keep Katmai open during working hours
• Walk over for quick questions
• Let conversations form naturally
• Use meetings only when structure is needed

What to Pay Attention To

Instead of asking “Did people use it?”, look for:

• Are meetings decreasing?
• Are decisions happening faster?
• Are questions answered more quickly?
• Do people feel more aware of each other?
• Is collaboration less forced?

Common Pilot Mistakes

• Treating Katmai like a meeting-only tool
• Over-scheduling inside the office
• Not spending enough time present
• Expecting instant behavior change

Deciding What to Do Next

A successful pilot usually ends with:

• Clear enthusiasm from participants
• Fewer meetings than before
• Stronger team awareness
• A desire to expand to more teams

If those signals are present, you’re ready to roll out.

Rolling Out with Confidence

After a pilot:

• Expand gradually
• Reinforce the office-first norm
• Support new teams with clear expectations
• Keep leadership visible in the space

Momentum matters. Don’t reset to old habits.

Want Help Running a Pilot?

If you’d like guidance designing or running your pilot, we’re happy to help.

A short conversation upfront can save weeks of confusion later.