Building Internal Tools That Teams Actually Adopt

An internal tool can be delivered and still go unused.

The problem isn't usually the tool. It's that you optimized for features instead of workflows.

**Features vs workflows:** A feature is "export to CSV." A workflow is "I need my weekly report in my inbox every Monday by 9am."

Designing around workflows can make a tool easier to adopt than adding features without understanding how the team works.

Three workflow principles:

1. **Eliminate a recurring pain point** Interview your team. Find a task they repeat and improve that workflow first. Agree on a baseline and a realistic target with the people who do the work.

2. **Move to where they already work** If your team lives in Slack, put what they need there. If they're in their email every morning, send summaries there. Don't ask them to adopt a new app.

3. **Reduce cognitive load** Every click, every decision point, every field makes adoption harder. Ruthlessly eliminate options. One well-designed workflow beats ten features.

**Measure adoption in context:** Choose a measure that reflects the workflow, such as the share of eligible tasks completed in the tool or how often intended users return to it. Establish a baseline, ask users what is getting in their way, and set a target that makes sense for the team's work. No single adoption threshold applies to every tool.

When adoption is low, revisit the problem being solved, the workflow fit, and the feedback from intended users.