--- title: "How Adam Weber and Emplify Used Peak OS to Build a Stronger Team Operating System" url: "https://www.collective-genius.com/insights/how-adam-weber-and-emplify-used-peak-os-to-build-a-stronger-team-operating-syste" author: "Jeff James Martin" organization: "Collective Genius" date_published: "2024-12-22T08:00:00.000Z" date_modified: "2026-07-11T02:29:48.582Z" reading_time_minutes: 15 cluster: "Operating Rhythm" tags: ["Operating Rhythm", "Peak OS", "Team Alignment", "Organizational Execution", "OKRs", "Accountability", "Growth Companies"] description: "Learn how Adam Weber and Emplify used Peak OS to simplify OKRs, improve Camp meetings, resolve blockers, increase accountability, and build Operating Rhythm." --- # How Adam Weber and Emplify Used Peak OS to Build a Stronger Team Operating System Adam Weber and Emplify used Peak OS to build a stronger team operating system by simplifying OKRs, reverse engineering from the three-year vision to the one-year and 90-day plans, refining objectives as a team, improving Camp meetings, resolving blockers, increasing weekly accountability, and creating momentum. The Emplify case study in Peak Teams shows how Operating Rhythm helps growth companies move from scattered effort to coordinated execution. A team operating system should make execution simpler. That is one of the clearest lessons from Adam Weber and Emplify in the *Peak Teams* book. Adam Weber, Co-Founder of Emplify, describes a common problem inside growth companies: many people have experience with OKRs, but not everyone has the same understanding of what OKRs are supposed to do. Some people treat OKRs as milestones. Some treat them as metrics. Some use the 70 percent rule. Some believe everything should be completed at 100 percent. Some teams write OKRs to stretch. Others write OKRs to commit. The result is confusion. The organization may be using the same words, but teams are not using the same operating system. That was one of the challenges Emplify faced before working with Peak. The company had experience with different OKR philosophies, but that experience did not automatically create clarity. In fact, it could slow decision-making because people brought different definitions, expectations, and habits into the process. Peak OS helped Emplify simplify the system. Instead of starting with complicated methodology, the process started with a direct question: “What are we trying to accomplish?” That simplicity mattered. It helped the team move past debate about OKR theory and into a stronger conversation about execution. For Adam Weber and Emplify, Peak OS became a way to build a stronger team operating system through vision, planning, OKRs, Operating Rhythm, accountability, decision-making, and momentum. ## Growth Teams Need Shared Operating Language Many teams think they are aligned because they use the same terms. But shared terms do not always create shared understanding. A leadership team may talk about OKRs, goals, priorities, metrics, projects, strategy, accountability, and execution. Everyone may nod in agreement. But underneath the language, people may mean different things. This creates hidden friction. One team may think an OKR is a commitment. Another may think it is an aspiration. One leader may think a key result is a metric. Another may think it is a milestone. One function may think the objective should be broad. Another may think the objective should be specific. One team may believe success means hitting the target. Another may believe success means learning from the stretch. That kind of misalignment slows execution. The Emplify case study shows why a team operating system must create shared language. Peak OS helped Emplify move away from competing OKR interpretations and toward a simpler, clearer way to discuss what the company was trying to accomplish. That is the foundation of Operating Rhythm. Before a team can execute together, it must understand the system together. ## Simplicity Creates Speed One of Adam Weber’s strongest observations was that Peak simplified the work. The key question was direct: “What are we trying to accomplish?” That question cuts through complexity. It avoids over-engineering. It forces the team to focus. It moves the conversation from methodology to outcome. Growth teams often lose time by debating process. They spend energy deciding whether a goal is an objective, a key result, a metric, a milestone, a project, or a task. Those distinctions matter, but they should serve execution, not replace it. Peak OS creates speed by making the system simple enough for teams to use. The question is not: Which OKR philosophy do we prefer? The question is: What are we trying to accomplish? Once that is clear, the team can discuss how to measure progress, what work is required, who owns the next steps, and what rhythm will keep execution moving. This kind of simplicity does not reduce discipline. It increases it. A simpler system is easier to align around, easier to repeat, and easier to use under pressure. ## Key Results Should Not Pull Teams Away From the Plan Adam Weber noticed a common problem with how teams use key results. When teams use key results only as metrics, they can drift away from their plan within weeks. This happens because the organization becomes focused on hitting numbers without staying connected to the strategy behind the numbers. That is a subtle but important execution problem. Metrics are useful. But metrics are not the whole plan. A company can chase a key result and lose sight of why the key result matters. A team can become focused on the number while ignoring the strategic choices, assumptions, and cross-functional work required to produce the outcome. This becomes especially dangerous when targets are overly ambitious. The team may set aggressive goals, create unrealistic product release schedules, and then realize later that the strategy was too ambitious from the start. Peak OS helps reduce this problem by keeping OKRs connected to a broader operating system. The key results do not float alone. They connect to vision. They connect to the one-year plan. They connect to the 90-day plan. They connect to team discussions. They connect to Operating Rhythm. They connect to learning. That connection keeps teams from treating key results as isolated numbers. ## Reverse Engineering Turns Vision Into Execution Adam described Peak’s approach as reverse engineering. The team began with a broad three-year vision, aligned around that direction, broke it down into a one-year plan, and then translated it into a 90-day plan. That structure matters. A three-year vision gives the company direction. A one-year plan creates strategic focus. A 90-day plan turns direction into execution. This sequence is important because many companies jump too quickly into quarterly goals. They ask teams to define OKRs before the company has enough shared understanding of the longer-term direction. That creates fragmented execution. Teams may write goals based on their functional priorities instead of the company’s strategy. The sales team may pursue one version of growth. The product team may prioritize another. Customer success may be preparing for a different operating reality. Finance may be planning around different assumptions. Peak OS creates alignment by working backward from the future. The vision gives context. The annual plan narrows focus. The 90-day plan defines what must happen now. This is how a team operating system connects aspiration to action. ## Everyone Contributes, Everyone Listens One of the strongest parts of the Emplify case study is the way Adam describes team participation. The process involved determining the most important objectives and key results as a team. Everyone contributed. Everyone listened. Everyone participated in refining the objectives down to what mattered most. That is a critical Operating Rhythm lesson. A strong operating system is not created by executives announcing goals and asking teams to comply. It is created through a process that helps the team think together. When everyone contributes, the team surfaces more information. When everyone listens, the team builds shared understanding. When everyone refines the objectives together, the organization becomes more focused. This does not mean every decision is made by consensus. It means the operating system creates the right conversation before the decision is made. That matters because people support what they understand. If teams do not understand the objective, they will interpret it differently. If they do not participate in refining priorities, they may miss the tradeoffs. If they do not hear the reasoning, they may execute locally instead of collectively. Peak OS strengthens execution because it creates alignment through participation, not just communication. ## A Strong Operating System Resolves Stumbling Blocks Adam explained that Peak was not a drastic departure from Emplify’s prior approach. It was more like a refined version that resolved earlier stumbling blocks. That is an important distinction. Many companies do not need to throw away everything they already know. They need to refine the system. They need to remove friction. They need clearer definitions. They need stronger rhythm. They need better meeting structure. They need a better way to narrow priorities. They need more useful accountability. They need the operating habits to support the goals they are already trying to achieve. Peak OS often works because it does not require companies to abandon their ambition, culture, or prior learning. It gives those elements a stronger operating structure. For Emplify, the value was not complexity. The value was clarity. The team already understood parts of OKR thinking. Peak helped them turn that experience into a more effective operating system. ## The First Camp Meeting Created a Turning Point Adam described a distinct turning point after Emplify’s first Camp meeting. He called it the “best internal meeting we’d ever had.” That is a powerful statement because it shows how quickly Operating Rhythm can change the way a team works. The value was not only positivity. It was efficiency. The team discussed blockers that might normally consume an entire meeting. Instead of getting stuck, they listed the challenges, focused on the most important discussions, and moved into decisions. This is what strong meeting rhythm does. It does not create meetings for the sake of meetings. It creates a structure for better execution. A weak meeting repeats updates. A strong meeting surfaces blockers. A weak meeting consumes time. A strong meeting creates decisions. A weak meeting ends with confusion. A strong meeting ends with ownership. Peak OS uses Camp meetings to help teams make progress through rhythm. The meeting becomes a place where issues are surfaced, prioritized, discussed, resolved, and moved forward. That is how rhythm becomes execution. ## Operating Rhythm Converts Blockers Into Momentum Every growth team has blockers. The difference is whether blockers are allowed to linger. In many organizations, blockers dominate meetings. Teams spend too much time circling the problem, explaining the context, debating symptoms, or revisiting old issues. The meeting becomes heavy. People leave with limited progress. Emplify experienced something different. The team listed challenges, focused on the most important discussions, and made decisions. Adam compared the momentum to a “debt snowball payoff.” That image captures how Operating Rhythm creates energy. Small wins compound. A resolved blocker creates momentum. A decision creates movement. Movement creates confidence. Confidence increases participation. Participation strengthens the rhythm. The team begins to trust that meetings will lead somewhere. That trust matters. When people believe a meeting will resolve something, they show up differently. They bring real issues. They prepare better. They engage more directly. They understand that the operating system is not performative. It is useful. ## Meetings Should Mean Something Gets Resolved One of Adam’s most important observations was that attending the meetings meant something was going to get resolved. That is the standard every team operating system should hold. A meeting should not only be a place where people listen and leave. It should create movement. This does not mean every issue can be fully solved in every meeting. But the rhythm should clarify what happens next. It should identify owners. It should move blockers forward. It should help the team understand whether the plan needs to change. Many companies tolerate meetings that do not improve execution. They review updates. They discuss problems. They end without decisions. They return to the same issues the following week. That kind of meeting weakens trust. Peak OS creates a different expectation. The meeting should help the team execute. The team should leave with more clarity than it had when it entered. That is what Emplify experienced. ## Weekly Accountability Changes Behavior Adam noticed that people became more alert when they knew they would be accountable every week instead of waiting until the end of a project. That is a major Operating Rhythm lesson. Accountability works best when it is frequent enough to shape behavior. If accountability only happens at the end of a project, the team may discover problems too late. Misalignment may persist for weeks or months. Blockers may remain hidden. The plan may become outdated before anyone adjusts it. Weekly accountability changes the cadence. It brings reality closer. It helps the team see what is working. It helps leaders identify what is blocked. It helps people make smaller adjustments earlier. It keeps the plan alive. This does not mean the team should be micromanaged. It means the team should have a rhythm that keeps commitments visible and learning active. Peak OS uses weekly accountability to help teams execute with more awareness and less drift. ## Operating Rhythm Helps Teams Adjust Plans Swiftly A plan is only useful if the team can adjust it when reality changes. Emplify’s experience showed this clearly. The team adjusted plans swiftly and saw a surge in pace. That is what Operating Rhythm makes possible. Without rhythm, adjustments happen randomly. A team notices a problem but waits too long to raise it. A leader sees a risk but does not know where to discuss it. A project drifts because no one creates the decision point. A goal becomes unrealistic, but the team keeps pretending it is still on track. With rhythm, the team has a recurring place to compare plan and reality. What changed? What is blocked? What needs to be adjusted? Which decision is required? Who owns the next step? This is how a company stays adaptive without becoming chaotic. Peak OS helps teams adjust plans while staying connected to the broader strategy. ## A Leaner Team Needed a Stronger Operating System Emplify implemented these changes during the COVID-19 pandemic. At the time, the company had reduced its team size by 20 percent. That was hard, but it also created a new operating reality. With a leaner team composed of top talent, productivity increased, and the company moved from a stagnant phase into a growth trajectory. This is an important lesson. A smaller team does not automatically become a stronger team. A leaner company still needs rhythm. It still needs clarity. It still needs priorities. It still needs accountability. It still needs a way to make decisions quickly. It still needs an operating system. In some ways, a leaner team needs an even stronger operating system because there is less room for wasted effort. Every meeting matters more. Every priority matters more. Every blocker matters more. Every missed handoff matters more. Peak OS helped Emplify turn a difficult moment into an execution advantage. The company had fewer people, but stronger focus, better rhythm, faster decisions, and more momentum. ## Operating Rhythm Can Restart Momentum Adam described Emplify as moving from a two-year stagnant phase to a growing trajectory. That is a major transformation. Stagnation does not always come from lack of effort. Often, teams are working hard but not moving together. The company may have too many priorities. The meeting rhythm may be weak. Blockers may not get resolved. Plans may not adjust quickly enough. Accountability may be too delayed. Teams may be unclear on what matters most. Peak OS helps restart momentum by creating a rhythm that turns scattered effort into coordinated progress. The work becomes more focused. Meetings become more useful. Decisions happen faster. Teams see small wins. The pace improves. The organization begins to believe that execution is changing. That belief matters because momentum is emotional as well as operational. Teams need to feel progress. Operating Rhythm helps create that feeling by making progress visible and repeatable. ## Operating Rhythm Supports Better Team Health Emplify was a company built around employee engagement and culture, so Adam Weber’s perspective on team operating rhythm is especially meaningful. Team health is not only about morale. It is also about clarity. People feel healthier when they understand what matters. They feel more engaged when meetings lead to decisions. They feel more confident when blockers get resolved. They feel more empowered when accountability is consistent. They feel more connected when everyone participates in refining priorities. They feel more motivated when small wins compound. Operating Rhythm supports team health because it reduces ambiguity. It gives the team a way to move through issues rather than carry them indefinitely. It helps people see progress. It creates a sense that the company is moving together. Peak OS strengthens team health by making execution less chaotic and more aligned. ## Operating Rhythm Is Not Bureaucracy Some leaders hear “operating system” and imagine bureaucracy. That is the wrong interpretation. A weak operating system creates bureaucracy. A strong operating system reduces friction. Emplify’s experience shows this clearly. The team did not become slower. It became faster. Meetings did not become heavier. They became more efficient. Accountability did not become punitive. It made people more alert and helped the team move. Operating Rhythm is not about adding unnecessary process. It is about creating the right cadence for execution. The goal is not more meetings. The goal is more progress. The goal is not more reporting. The goal is better decisions. The goal is not more structure. The goal is enough structure to help the team move together. Peak OS helps companies find that balance. ## Why This Case Study Belongs in Operating Rhythm The Emplify case study belongs in the Operating Rhythm cluster because it shows what happens when rhythm becomes practical. The team did not only define objectives. It created a cadence for review. It did not only list blockers. It resolved them. It did not only talk about accountability. It made accountability weekly. It did not only create plans. It adjusted them quickly. It did not only create energy. It translated energy into execution. This is what Operating Rhythm should do. It should help teams maintain focus, address reality, make decisions, and keep moving. Emplify’s story shows how a team operating system becomes stronger when the rhythm is simple, participatory, accountable, and useful. ## What Leaders Can Learn From Adam Weber and Emplify The Emplify case study gives leaders several important lessons. First, OKR experience does not always create OKR clarity. Second, a direct question can simplify execution. Third, key results must remain connected to the plan. Fourth, reverse engineering from the three-year vision to the one-year plan to the 90-day plan creates alignment. Fifth, everyone should contribute, listen, and participate in refining objectives. Sixth, meetings should help resolve blockers, not simply discuss them. Seventh, weekly accountability changes behavior. Eighth, leaner teams need stronger rhythm. Ninth, Operating Rhythm can restart momentum. Tenth, a stronger team operating system can support better execution and a healthier team. These lessons matter because growth companies often do not need more complexity. They need a better rhythm. ## Peak OS and the Emplify Lesson Peak OS helped Emplify build a stronger team operating system by simplifying how the team discussed objectives, connecting the three-year vision to the one-year and 90-day plans, creating participation in objective refinement, improving meeting efficiency, resolving blockers, increasing weekly accountability, and helping the team regain momentum. That is the power of Operating Rhythm. It turns the operating system into a lived habit. The team knows what it is trying to accomplish. The team knows where the blockers are. The team knows which conversations matter most. The team knows that meetings are meant to resolve issues. The team knows accountability will happen every week. The team knows the plan can adjust when reality changes. Peak OS gives that rhythm structure. And that structure helps teams execute. ## Final Thought The lesson from Adam Weber and Emplify is that a team operating system should make execution clearer, faster, and more useful. It should simplify the work. It should help the team define what it is trying to accomplish. It should connect vision to planning. It should create space for everyone to contribute and listen. It should make meetings more effective. It should resolve blockers. It should create weekly accountability. It should help teams adjust quickly. It should build momentum. Emplify used Peak OS to move from scattered OKR interpretations and stalled momentum toward a stronger Operating Rhythm. That is what growth companies need. Not more process. Not more theory. Not more complicated goal systems. A team operating system that helps people execute together. ## Related Insights What Is Operating Rhythm? [https://www.collective-genius.com/insights/what-is-operating-rhythm-mq4qywur](https://www.collective-genius.com/insights/what-is-operating-rhythm-mq4qywur) What Is Peak OS? [https://www.collective-genius.com/insights/what-is-peak-os-mq7jqhdx](https://www.collective-genius.com/insights/what-is-peak-os-mq7jqhdx) What Is Organizational Execution? [https://www.collective-genius.com/insights/what-is-organizational-execution-mq4rcx9p](https://www.collective-genius.com/insights/what-is-organizational-execution-mq4rcx9p) What Is Team Alignment? [https://www.collective-genius.com/insights/what-is-team-alignment-mq4qf6p1](https://www.collective-genius.com/insights/what-is-team-alignment-mq4qf6p1) What Is Organizational Visibility? [https://www.collective-genius.com/insights/what-is-organizational-visibility-mq4qlbpj](https://www.collective-genius.com/insights/what-is-organizational-visibility-mq4qlbpj) ## Key Takeaways - Emplify had experience with OKRs, but different interpretations slowed decision-making. - Peak OS simplified the work by asking, “What are we trying to accomplish?” - Reverse engineering from the three-year vision to the one-year plan and 90-day plan helped create alignment. - Everyone contributed, listened, and participated in refining the most important objectives. - Emplify’s first Camp meeting became a turning point because blockers were surfaced and resolved more efficiently. - Weekly accountability made the team more alert and helped execution move faster. - Peak OS helped Emplify restart momentum and move toward a successful business exit. ## Frequently Asked Questions ### Who is Adam Weber? Adam Weber is featured in the *Peak Teams* book as the Co-Founder of Emplify. His case study describes how Emplify used Peak OS to simplify OKRs, improve meeting rhythm, increase accountability, and build stronger execution momentum. ### What is the Emplify case study about? The Emplify case study is about how a growth company used Peak OS to create a stronger team operating system through clearer objectives, reverse-engineered planning, better Camp meetings, blocker resolution, weekly accountability, and faster execution. ### How did Peak OS help Emplify? Peak OS helped Emplify simplify OKRs, connect the three-year vision to the one-year and 90-day plans, refine objectives as a team, improve meeting efficiency, resolve blockers, increase weekly accountability, and restart momentum. ### What did Adam Weber say stood out about Peak OS? Adam Weber said the simplicity of creating an objective stood out. The direct question was: “What are we trying to accomplish?” ### Why are Camp meetings important in Peak OS? Camp meetings are important because they create a rhythm for surfacing blockers, focusing on the most important discussions, making decisions, assigning ownership, and keeping execution moving. ### How does Operating Rhythm improve execution? Operating Rhythm improves execution by creating a recurring system for reviewing progress, resolving blockers, making decisions, adjusting plans, and reinforcing accountability. ### What can leaders learn from Emplify? Leaders can learn that a stronger team operating system does not need to be complicated. It needs to create clarity, rhythm, participation, accountability, decision-making, and momentum. Source: https://www.collective-genius.com/insights/how-adam-weber-and-emplify-used-peak-os-to-build-a-stronger-team-operating-syste