3 actionable ways you can add context to documentation

The “why” behind what your team is doing is just as important as the “how.”

The “how” is operational, and often lives in documentation. Ask anyone at your company how to submit PTO, and they’ll all probably point you to the same document. It’s all about execution.

Without the “why,” the “how” rings hollow.

It’s a bit like wearing blinders. Teams see the ground in front of them, but don’t know where they’re going. That can be dangerous leading to apathetic teams who feel like they don’t have any real agency in their work.

The “why” (or giving context) rarely makes it into written documentation despite its importance. But it can be something that drives your team’s best work.