Most corporate leaders enter their careers believing that success means doing everything asked of them. Every project, every initiative, every committee someone volunteers them for. Work hard, say yes, clear the to-do list. That belief isn't just wrong. It is the thing that most reliably guarantees you will spend your career operating below your potential. The people who figured out a better way earliest? Teachers.
This is the third and final post in a series exploring what corporate leaders can learn from the teaching profession. If you're joining mid-series, Part I introduced the concept of work plans as a communication tool, and Part II went deeper into how teachers structure feedback and accountability. Here, we close with the concept I think matters most: prioritization.
The Promotion Conversation That Changed Everything
When I was first promoted to Director-level at a Fortune 50 company, I expected a conversation full of encouragement. The standard congratulations, some reassurance, a few words about the road ahead.
Instead, my manager sat me down and said something I never forgot.
"We will always give you more work than you can possibly complete," she said. "That's intentional."
I asked the obvious question: how was I supposed to succeed under those conditions?
Her answer was direct. "Anyone can just do the tasks they're given. We're paying you to filter through all the work, identify the 80 to 90 percent that is most important, and drop the bottom 10 to 20 percent."
She wasn't asking me to cut corners. She was asking me to make consequential choices about what actually mattered. Your managers and your shareholders didn't hire a robot to execute tasks on demand. They hired you to determine what is worth executing and what is not.
That piece of advice stayed with me through every role I held afterward. And when I made the decision to leave the corporate world and take a job teaching middle school engineering, I discovered that teachers had been operating this way for decades. The only difference: they had a name for it, and a system built around it.
The Firehose Before a Single Day of Class
During the summer before my first teaching assignment, I did what any conscientious new hire would do: I tried to get organized.
The list of things I needed to learn, implement, and manage before September was staggering. There was the STEAM curriculum from PLTW (Project Lead The Way), which gave me a solid structure for what to teach. Then an Advisory class with its own Social-Emotional Learning requirements. Then accommodations for English language learners. Then students with 504 plans or IEPs, each with adjustments baked into every lesson.
Then came the meetings. Department meetings. Grade-level team meetings. Professional Learning Community sessions with engineering teachers across the district. A Community Connections committee I had been "volun-told" to join. And quarterly observations with all the documentation those required.
All of that was before a single student walked through my door. Before one parent called about behavior. Before one project was graded.
I'm not sharing this to compare the difficulty of teaching to corporate work. Both are demanding in different ways. The point is this: the concept of prioritization isn't a nice-to-have in education. It is built into the infrastructure of how the profession operates. Because the alternative — trying to teach every student everything — is obviously impossible. Corporate life, however, often operates as though that alternative is the default.
What Priority Standards Are and Why They Work
Teachers operate within a framework of Standards: state-directed learning objectives that define what students are expected to master in each subject each year. There are a lot of them. Too many to reliably hit in 180 school days, which is precisely the point.
So the education system doesn't just list Standards. It identifies Priority Standards: the non-negotiable outcomes that every student in every classroom, district-wide, must achieve before the year ends. These are the headlines. Everything else is secondary, addressed once the Priority Standards are secure.
The distinction matters for two reasons.
First, it forces honesty. When you name your Priority Standards, you simultaneously acknowledge that everything else on the list has been ranked lower. That is psychologically difficult for most leaders, who prefer to hold everything at maximum importance. Priority Standards remove that option.
Second, it creates alignment. When an entire district operates from the same Priority Standards, teacher conversations stop being about what each person happens to feel like covering this month and start being about whether students are actually reaching the outcomes that matter. That is a very different conversation, and it produces very different results.
The Professional Learning Community Model
One of the most powerful mechanics in education is the Professional Learning Community, or PLC: a regularly scheduled forum where teachers of the same subject, across a school or district, gather to discuss their progress on the Priority Standards they share.
Not general progress. Progress on the specific shared outcomes that have been agreed upon as the most important for the year.
What this does is remarkable. It makes each individual teacher's prioritization decisions a matter of collective accountability. You don't arrive at your Priority Standards alone. You work toward them alongside a group of peers who teach the same students in different classrooms and can tell you when your assumptions about what matters are off.
Think about the corporate parallel. It would strike any reasonable person as strange if every teacher in every district taught completely different material with completely different goals. Yet most companies tolerate exactly that situation inside their own walls. Ask five managers on the same leadership team what the organization's top three priorities are, and you will often hear five different answers. That misalignment isn't a people problem. It is a Priority Standards problem.
The "What Would Happen?" Filter
Most corporate leaders don't have a district curriculum office handing them Priority Standards. So here is the exercise that functions as the equivalent.
Start by writing down the outcomes that must happen for your team and your organization to call the year a success. Be specific. Not "grow revenue" but "close X enterprise accounts in Q3." Not "improve culture" but "complete manager coaching certification with 80 percent of the leadership bench by October."
Then, for each item on that list, ask one question: "What would happen if this didn't occur?"
If the answer is "a lot, this directly affects our ability to hit the core number," you have identified a Priority Standard. Keep it on the list and protect it.
If the answer is "not much, honestly," you have identified an item that has been given false urgency by volume rather than actual strategic weight. Move it down, delegate it, or drop it entirely.
This is the same filter your managers were using when they assigned you more work than was possible. They expected you to run this test on everything that landed on your desk. Most leaders don't realize they are supposed to be running it themselves, continuously, on behalf of everyone who reports to them.
From Priority Standards to Work Plans
Once you have identified your organization's 3 to 5 Priority Standards for the year, the work isn't done. Those high-level priorities need to cascade.
Start with the annual priorities. Then break them into quarterly group actions: what does each team need to complete this quarter in order to move the priority forward? Then further into individual work plans: what does each person need to accomplish this month to contribute to the quarterly action?
This is the structure discussed in Part I of this series. The work plan is not a task list. It is a bridge between the organization's Priority Standards and each individual's day-to-day decisions. When the bridge is built correctly, every person on the team can draw a direct line from what they are working on this week to one of the outcomes the organization has committed to achieving this year.
The cascade only holds if you review it regularly. Business conditions change. People complete their goals. New priorities emerge. If you set the work plans in January and don't revisit them until December, you have left your results to chance. Monthly reviews, or quarterly at minimum, are what keep the cascade alive and honest.
The Risk of Treating Everything as a Priority
There is a cognitive cost to operating without Priority Standards that rarely gets named directly.
When everything is important, nothing feels important. Urgency becomes noise. Teams lose the ability to distinguish between a genuine strategic commitment and a request that someone made feel urgent by being loud about it. High performers get pulled toward whatever is loudest rather than whatever is most consequential. Output climbs. Impact plateaus.
This isn't a discipline failure. It is a leadership infrastructure failure. The team doesn't have a clear shared signal for what the 80 to 90 percent is, so they guess. They guess differently. And the divergence compounds over quarters and years into a pattern where the organization works extremely hard and still misses the things that matter most.
Priority Standards give your team that shared signal. Not because they're a clever management technique, but because they make the most important things legible. You can talk about them in reviews. Measure progress against them. Hire toward them. Push back on scope creep using them as the reference point.
Three Actions to Put This Into Practice
Prioritization at the organizational level doesn't require a retreat or an outside consultant. It requires a focused conversation and the discipline to protect what comes out of it.
Here is where to start.
First, convene a small group of peers: your leadership team, your functional leads, your most senior direct reports. Write down the 3 to 5 outcomes that must happen this year for the organization to succeed. Use specific language. Test each one with the "What would happen?" filter. If the filter doesn't eliminate at least two or three items from your first draft, your list is still too long.
Second, cascade those Priority Standards into quarterly group actions for each team or function, then further into individual monthly work plans. Make sure every person on your team can draw a direct line from their work plan to at least one of the annual Priority Standards. If they can't, the cascade is broken somewhere and needs to be repaired.
Third, put a standing monthly review on the calendar and protect it. The Priority Standards will need to update as the year progresses. Work plans will need to change. New priorities will emerge. The review is what keeps the system honest rather than becoming another set of goals that no one looks at after Q1.
Adolescents, it turns out, are the ultimate litmus test for communication. If you can hold their attention and actually move them toward a goal, you can do it with anyone. That lesson applies everywhere, including in the boardroom. And the first step is knowing what the goal actually is.
Great communication is what makes every part of this work, from the conversation where you name the priorities, to the monthly reviews where you hold the line on them. That is where Braintrust works with leaders across the industries we serve. If you are ready to talk about what a coaching and communication framework looks like inside your organization, reach out here.
