Connect an individual's goals to team and company goals so people understand how their work contributes.
Why alignment matters and how OKRs help
Connecting individual work to the bigger picture
When people do not understand how their daily work connects to the team or company's goals, three problems appear. First, motivation drops — it is hard to care about a task when you cannot see why it matters. Second, focus scatters — people optimize for the wrong things. Third, effort gets wasted — teams duplicate work or pull in opposite directions without realizing it.
A manager's job is to cascade context downward: to take the company's direction and translate it into goals that are meaningful and actionable for each person on the team. This does not mean simply passing a number down the chain. It means explaining the reasoning — why this goal, why now, and how it fits into what the organization is trying to achieve.
One well-known tool for making alignment visible is OKRs (Objectives and Key Results). The idea was developed by Andy Grove at Intel in the 1970s and later popularized by John Doerr, who brought it to Google in 1999. An Objective is a qualitative, inspiring direction: where do we want to go? Key Results are quantitative milestones that tell you whether you got there. OKRs are used here as one example of an alignment tool, not as a system every team must adopt.
Here is a worked example. Company objective: "Become the most trusted vendor in our market segment." Team objective (derived from above): "Cut support response time in half this quarter." Individual goal (derived from team): "Resolve 95% of my assigned tickets within 4 hours by September 30." Each level is specific to the person's role, but a straight line connects individual effort to company direction. A manager who can draw that line for every team member has done the core work of alignment.
Lesson notes
Connecting individual work to the bigger picture
When people do not understand how their daily work connects to the team or company's goals, three problems appear. First, motivation drops — it is hard to care about a task when you cannot see why it matters. Second, focus scatters — people optimize for the wrong things. Third, effort gets wasted — teams duplicate work or pull in opposite directions without realizing it.
A manager's job is to cascade context downward: to take the company's direction and translate it into goals that are meaningful and actionable for each person on the team. This does not mean simply passing a number down the chain. It means explaining the reasoning — why this goal, why now, and how it fits into what the organization is trying to achieve.
One well-known tool for making alignment visible is OKRs (Objectives and Key Results). The idea was developed by Andy Grove at Intel in the 1970s and later popularized by John Doerr, who brought it to Google in 1999. An Objective is a qualitative, inspiring direction: where do we want to go? Key Results are quantitative milestones that tell you whether you got there. OKRs are used here as one example of an alignment tool, not as a system every team must adopt.
Here is a worked example. Company objective: "Become the most trusted vendor in our market segment." Team objective (derived from above): "Cut support response time in half this quarter." Individual goal (derived from team): "Resolve 95% of my assigned tickets within 4 hours by September 30." Each level is specific to the person's role, but a straight line connects individual effort to company direction. A manager who can draw that line for every team member has done the core work of alignment.