Week 46 Day 4: Do You Understand Why Your Work Matters?

This question measures whether you have successfully communicated Commander's Intent (Week 18) and connected daily work to the Value Pyramid (Weeks 11-14). The test is simple: stop a team member at random and ask them to explain why their current project matters to the business. If they can answer in two sentences, you have communicated well. If they describe what they are doing but not why, you have communicated tasks but not purpose.

Here is how to diagnose and repair a 'no' on this question. The diagnosis: a low score on this question usually means one of three things. Possibility one -- you have not communicated the why. You assigned the work with instructions on what to build and how to build it, but you skipped the context. The team knows the tasks but not the purpose. This is the most common cause and the easiest to fix. Possibility two -- you communicated the why, but it did not land. You explained the purpose once, in a meeting or an email, but the explanation was too abstract, too brief, or delivered at a moment when the team was focused on other things. The communication happened but the understanding did not. Possibility three -- the why changed but you did not update. The original purpose was clear, but priorities shifted, strategy evolved, or the business context changed, and you did not re-communicate the why in the new context. The team is still operating on the original understanding, which is now outdated. The repair depends on the cause. For possibility one: add a 'why this matters' statement to every project kickoff, every sprint planning session, and every major task assignment. Use the Commander's Intent format from Week 18: purpose (why we are doing this), key tasks (what we are doing), and end state (what success looks like). For possibility two: follow the communication rule of seven -- important messages need to be communicated at least seven times through multiple channels before they are reliably internalized. Say it in the kickoff meeting, write it in the project brief, reference it in standup, connect individual tasks to it in one-on-ones, and revisit it in sprint reviews. For possibility three: when strategy or priorities shift, explicitly update the team on how the shift changes the why for their current work. 'Last month, the purpose of this project was to improve retention. The business context has shifted -- our retention is stable, but acquisition is lagging. The same project now matters because it improves the onboarding experience for new users, which supports acquisition. The work is the same; the reason it matters has changed.' The meaning connection does not stay connected by itself. It requires regular maintenance -- revisiting why the work matters as context evolves.

The meaning deficit is documented by Rosso, Dekas, and Wrzesniewski (2010) in their comprehensive review of 'the meaning of work,' which identifies four primary sources of work meaning: self (identity expression), others (relationships and service), work context (organizational mission), and spiritual life (transcendence). Their review found that the work context source -- understanding how one's work contributes to a meaningful organizational purpose -- was the source most directly influenced by leadership behavior, and that leaders who explicitly and repeatedly connected individual tasks to organizational purpose produced teams with 30% higher engagement and 25% lower turnover intention. The 'rule of seven' in organizational communication is supported by research by Kotter (1995) on 'leading change,' which found that leaders consistently underestimated the amount of communication required by a factor of 10 -- they believed one clear communication was sufficient, while employees required 5-10 repetitions across multiple channels before the message was reliably internalized. The Commander's Intent connection (Week 18) is validated by research by Shamir, House, and Arthur (1993) on 'the motivational effects of charismatic leadership,' which found that leaders who communicated purpose (why the work matters) rather than just tasks (what the work is) produced significantly higher intrinsic motivation in their teams, because purpose communication activated the team members' sense of identity and meaning, transforming compliance into commitment.