Change Management & Team Communication

How to explain Katmai internally and support lasting adoption.

Katmai works best when teams understand why the way they work is changing, not just what tool they’re using.

This guide helps you communicate the shift clearly, set expectations early, and support lasting adoption without friction.

Start with the Why

Before talking about features, explain the problem Katmai is solving.

Remote work didn’t fail because people weren’t working hard.
It failed because visibility, proximity, and spontaneous communication disappeared.

Katmai brings those back.

Position Katmai as:

• A shared place, not another tool
• A way to reduce meetings, not add them
• A return to natural communication, not forced process

Be Explicit About What’s Changing

Clarity beats enthusiasm.

Tell your team plainly:

• When we need to talk or meet, we go to the office
• We won’t default to internal meeting links anymore
• Being present doesn’t mean being interrupted
• It’s okay to be quiet and focused in the office

Unspoken assumptions cause resistance. Say it out loud.

What’s Not Changing

Reassure people early.

Katmai does not mean:

• Constant monitoring
• Being “always on”
• Losing focus time
• Replacing every existing tool

Set Simple Operating Norms

You don’t need a long rulebook.

A few clear norms are enough:

• Keep Katmai open during working hours when possible
• Walk over for quick questions instead of messaging
• Use meetings only when structure is needed
• Signal availability clearly

Norms matter more than documentation.

Model the Behavior

Adoption follows leadership behavior, not announcements.

Leaders should:

• Spend visible time in the office
• Walk over instead of scheduling
• Hold meetings inside Katmai
• Be present even when not talking

If leaders treat Katmai as optional, the team will too.

Support the First Few Weeks

Early moments matter.

In the first weeks:

• Answer questions quickly
• Gently redirect old habits
• Celebrate spontaneous collaboration
• Normalize awkwardness early on

Most resistance fades once people experience the benefits.

Use Language People Can Repeat

Give your team simple phrases they can use:

• “Let’s go to the office.”
• “I’m around if you want to walk over.”
• “We don’t need a meeting for that.”

Shared language reinforces shared behavior.

Watch for the Right Signals

Adoption isn’t about usage charts alone.

Look for:

• Fewer meetings
• Faster decisions
• Less internal messaging
• More natural collaboration
• Stronger team awareness

These are signs Katmai is becoming part of how work happens.

When Teams Struggle

If a team isn’t engaging:

• Revisit expectations
• Increase leadership presence
• Encourage time spent in the office
• Reset norms, not features

Behavior change usually needs reinforcement, not more tooling.

Want Help Driving Adoption?

If you want help crafting internal messaging, setting norms, or supporting teams through the transition, we’re happy to help.

Adoption is a process. You don’t have to manage it alone.