One of the most powerful strategic resets we've adopted at Pawland at the end of each year is a Keep-Kill-Change audit. It's simple in structure but incredibly revealing when done with honesty and data-driven insights. From my experience, the biggest benefit of this audit is clarity. When a company grows, especially a service-focused one like ours-tasks, processes, and even goals can accumulate faster than we realize. The Keep-Kill-Change framework forces us to slow down and evaluate: What is clearly working and should be protected (Keep) What is draining time, morale, or resources without measurable ROI (Kill) What is valuable but needs rethinking, upgrading, or automation (Change) The potential trap in this process is turning it into a "fault-finding" session instead of a growth-focused exercise. It's important that teams don't feel like the intention is to judge performance, but rather to improve the system. We avoid this trap by assessing processes and outcomes, not people. For example, instead of saying, "Customer onboarding is delayed because the team isn't fast enough," the focus becomes, "Our onboarding tools aren't scalable, what needs to evolve so the team can succeed faster?" If I could give one recommendation for executing an effective end-of-year Keep-Kill-Change audit, it would be to ground the discussions in evidence, not opinions. Look at customer feedback, operational metrics, revenue contribution, time-to-completion, and employee experience. Some of our best decisions came from listening to frontline insights, the people who use the workflows daily always know where the inefficiencies really are. When done intentionally, this audit doesn't just optimize workflows, it reinforces a culture of constant improvement, transparency, and psychological safety. It sets the tone for the new year: we're keeping what makes us great, respectfully retiring what no longer serves us, and evolving into what we need to become next. Skandashree Bali CEO & Co-Founder, Pawland
Most organizations begin the year with ambitious goals. Fewer ask the harder question: What should stop? Gallup's 2024 workplace report shows global employee engagement slipped to 21 percent, contributing to an estimated 438 billion dollars in lost productivity. Leaders often respond by adding new initiatives, but rarely by examining the work that is quietly draining the most energy and attention. Frameworks like Keep Kill Change have grown popular for good reason. But on their own, they solve only half the problem. Without clarity on core strategy, eliminating tasks simply creates space that gets refilled with more busywork. The organizations gaining momentum today are not doing more, they are doing less with intention. The shift happens when pruning becomes a cultural habit And the most valuable insights rarely come from the top. They come from the people closest to the work, the frontline, customer facing, and revenue generating teams who see inefficiencies long before senior leaders do. In my superintendent role and in my coaching work with executives and entrepreneurs, three outcomes appear consistently: 1. Hidden drains finally surface. Recurring meetings, legacy committees, outdated workflows, and inherited tasks become visible. 2. Leaders regain capacity for strategic priorities. Pruning low impact activities frees time for planning, innovation, culture building, and customer value. 3. Burnout declines as alignment strengthens. When teams understand the "why" behind their work, friction decreases and ownership rises. In my own leadership role, applying this approach revealed that several long standing committees had outlived their purpose, created for problems long since solved. Streamlining and realigning those structures freed capacity and sharpened focus. In my work with leaders I use my Strategic Pruningtm Model a four filter framework designed to help leaders understand not just what to stop, but why work accumulates in the first place: Keep: Mission critical work tied directly to strategy Strengthen: Work that matters but needs refinement Prune: Tasks draining more energy than they return Stop: Work no longer aligned with direction or purpose Strategic Pruning gives employees a structure to focus on the right work, reduce noise, and align daily effort with the organization's objectives. A disciplined, ongoing pruning rhythm creates the clarity, capacity, and momentum organizations need to move confidently into what comes next.
A Keep Kill Change audit helps teams slow down and notice what shapes their daily work. Our team has used it to make tough choices feel lighter and more thoughtful. It guides people to see both the emotional and practical sides of what they do each day. I once supported a team that decided to keep their midweek check-in because it helped them build stronger relationships. They also changed their handoff rules so projects moved with a steady rhythm. The shift removed steps that created friction for new members and allowed them to settle in with ease. These choices gave the team better flow and more space to focus on shared goals. A simple and thoughtful approach like this helps create a healthy work culture.
Over the years, I have led so many teams, and I have personally noticed the majority of troubles in workflows come from old processes, half-finished projects, and outdated content. This is why doing a Keep-Kill-Change audit at year-end is one of the most effective ways to reset priorities and remove operational clutter. We often keep experimenting with new tools and technologies with the evolving needs, and this often drains budget and time if not filtered with time. I feel nothing will change unless you change your working method. A keep-kill-change audit helps us to see the big picture and identify what is working for the organization and what needs to be removed. Teams usually continue using the same old processes because they have a habit of doing it that way, and the method has always worked. This audit motivates everyone to look at workflows, tools, meetings, responsibilities, and many other angles with a fresh view. Here is how you can use it: - Keep the things that are working well and need to be updated or improved. - Kill or remove anything that is draining your work, specific tasks, tools, or projects that no longer make sense. - Change the things that have potential to give great results but need a new direction, such as improving workflows, restructuring projects, or anything Lastly, to make this audit effective, use data like time spent, costs, outcomes, and involve people from different levels in important decisions. If you follow this, you will definitely enter the new year with sharper focus, less waste, and your teams will feel more aligned and motivated.
I have used a Keep, Kill, or Change audit at Wisemonk for the past few years, especially during our rapid growth phases. It has become one of the best ways to reset priorities and ensure our team starts the new year with clarity rather than confusion. The biggest benefit is that it encourages honest reflection without judgment. When you ask what to keep, kill, or change, people feel more comfortable questioning long-standing processes that may no longer be helpful. Many leaders make the mistake of treating the audit like a simple checklist. To gain real insight, you need to create a safe space where team members can speak openly. In one of our early audits, I noticed our team hesitated to "kill" certain workflows because they feared it would be seen as criticism of someone's past work. Once we clarified that the goal was improvement, not blame, the quality of insights improved significantly. One method that has worked well for us is splitting the audit into two parts. First, we conduct the exercise within smaller teams to encourage honesty. Then, we gather the insights at the leadership level to identify common themes across the organization. This helped us identify patterns like unnecessary handoffs that slowed down onboarding and repeated steps in compliance reviews. Some of our best operational improvements came directly from these observations. A Keep, Kill, or Change audit is most effective when it leads to action within the first few weeks of the new year. Even one small visible win can build trust in the process and encourage greater participation next time. For leaders, this exercise serves as a reminder that improvement doesn't come from dramatic changes. It stems from consistent, thoughtful adjustments that keep the company focused on its future rather than its past.
In aerospace manufacturing, year-end reviews often highlight the volume of parts a supplier has produced that do not immediately appear to meet specification, but may still be fit for purpose. These potentially non-conforming products are assessed to determine whether they should be accepted, reworked or rejected. All three outcomes carry implications. Even parts that are ultimately accepted can become expensive if they have sat in assessment queues for too long or if the evaluation drags on without resolution. The cost lies not in the acceptance itself, but in the time and resources consumed during the assessment process. Ultimately, the aim of the "keep-kill-change" approach is to unclog the workflow and reduce the backlog, freeing resources and ensuring the manufacturer does not carry "difficult" parts into the new year. The traps lie in the judgment calls. Accepting too many borderline items risks wasted effort and prolonged assessment cycles. Rejecting without considering cost or customer impact can cause parts shortages that disrupt production schedules. Rework can be costly, time consuming and does not always guarantee a conforming part at the end. A practical tip is not to make these decisions in isolation. Convene a small team of no more than five, including representatives from different but vital functions. That way balanced perspectives are gained without clashing or too many opinions across all key considerations. Done correctly, the result is a leaner list and a better-focused start to the year.
I've conducted Keep-Kill-Change audits at Fulfill.com every year since we launched, and the biggest trap I see leaders fall into is treating it like a cost-cutting exercise instead of a strategic optimization. The real value comes when you approach it as an honest assessment of what's actually moving your business forward versus what's just creating motion. At Fulfill.com, I learned to structure these audits around three critical questions. First, what processes or initiatives directly contributed to revenue growth or customer satisfaction this year? Those are obvious keeps. Second, what's consuming resources but delivering minimal impact? Those are your kills. The hardest category is change, where something has potential but isn't working in its current form. I've found that about 60 percent of what we evaluate ends up in this change category, which tells you most things aren't completely right or wrong. Here's what works from my experience: I involve team leads from every department, not just executives. When we evaluated our warehouse partner onboarding process last year, our operations team identified that we were requiring 47 data points upfront when only 12 were actually necessary for decision-making. That insight came from the people doing the work daily, not from my desk. We killed 35 data requirements and cut onboarding time by half. The potential trap is moving too fast. I give our team four weeks to gather data before we make final decisions. We track metrics like time spent, resources consumed, and outcomes achieved. Without data, these audits become opinion contests where the loudest voice wins. I also learned to separate people from processes. When we kill a process, we're not killing someone's value to the company. I'm explicit about this. Last year, we eliminated a manual inventory reconciliation workflow that was taking 15 hours weekly, but we redirected that team member to improving our warehouse matching algorithm, where they've added significantly more value. One specific framework I use: anything we keep must have a clear owner and defined success metrics for the next quarter. Anything we change gets a 90-day trial with specific checkpoints. This prevents the audit from becoming an annual event that everyone forgets about by February. The most important insight from running a 3PL marketplace is that optimization is continuous. These year-end audits formalize what should be happening quarterly at a smaller scale.
I've used Keep-Kill-Change audits with leadership teams for years, and the biggest shift comes when you treat the exercise not as a housekeeping task but as a moment of strategic honesty. It forces teams to examine where their time, talent, and attention actually went during the year, instead of where they assumed it went. When done well, it sharpens priorities and gives people permission to drop the work that no longer serves the business. The most useful audits start with real data. I look at how teams spent their weeks, what initiatives produced momentum, and where friction kept showing up. Patterns tend to reveal themselves fast. Some activities are clear "keeps" because they drive growth or support a long-term direction. "Kills" are usually tied to legacy habits, pet projects, or tools that no longer match the stage the business is in. The "change" category is often where the upside lives. These are workflows or roles that still matter but need redesign to produce the outcomes the company actually wants. The biggest trap I see is turning the audit into a political exercise. If leaders start protecting their own initiatives instead of looking at impact, the process loses its value. Another trap is focusing only on what to cut. Teams do their best work when the audit creates clarity about what really matters, not just what should disappear. When the exercise is handled with transparency and grounded in outcomes, it becomes a powerful reset. It improves focus, builds trust across functions, and gives teams a shared understanding of what they're walking into in the new year. I've seen companies unlock meaningful gains in performance, retention, and decision making simply because they finally stopped spreading themselves thin and committed to the work that moves the needle.
We see the audit as a way to honor our mission. Every dollar saved returns to patients, communities, and frontline staff. That perspective guides every Keep, Kill, or Change decision respectfully. Purpose protects the integrity of the entire process. One major trap is making decisions too quickly without data. We learned to validate assumptions with measurable outcomes before final choices. This prevents unnecessary disruption across interconnected workflows. The audit works best when disciplined patience meets bold improvement.
Sometimes growth feels like running a marathon where the finish line keeps moving. At spectup, I've seen companies sprint ahead, only to realize halfway through that their old playbook is now full of cracks. That's when a brutally honest year-end Keep-Kill-Change audit can feel like a lifeline, a chance not just to fix what's broken, but to reset the whole rhythm before burnout sets in. One client had exploded in size over the year, what used to work suddenly felt like quicksand trapping their teams in endless frustrations. The framework is straightforward but powerful: first, figure out what to Keep, those processes, tools, and habits that actually deliver results and keep the engine humming. Then, Kill, the time-sucking, painful redundancies and outdated practices that got stuck in the cracks as the company grew too fast. Last, Change, pinpoint where fresh thinking, new tech, or better communication can unlock the next level. The most eye-opening part? Getting the whole team involved. When every voice gets to air frustrations, solutions, and ideas, magic happens. We uncovered a reporting tool duplicated across three departments, a classic case of "everyone's doing the same thing but no one feels it's theirs." Killing that tool and centralizing data didn't just save dozens of hours a week; it gave people back what they sorely missed: time to focus on the work that moves the needle. Another small but powerful change was tweaking meeting cadences and reporting flows, which boosted morale more than we expected, cutting down "death by meeting" fatigue and making work feel smoother. But beware the trap: this isn't a checkbox exercise. The audit has to dig deep, not just skim metrics but capture raw, honest feedback. Balance the numbers with real stories from the trenches. The only audits that truly stick and spark growth are the ones where leadership listens and acts decisively. In my experience at spectup, a well-run Keep-Kill-Change audit is a culture win, more like you can say, a signal to your teams that their voices drive change and the company is moving as one. Done right, it becomes a powerful repeatable ritual that clears the fog, sharpens focus, and builds unstoppable momentum heading into a new year.
I've run Keep-Kill-Change reviews at RiverCity for 15+ years while growing from 15 to 75 employees. The breakthrough came when I stopped scheduling these as "audits" and started tracking simple metrics monthly that make the January decisions obvious. We track three numbers religiously: order-to-delivery time, error rate per production line, and revenue per employee. Two years ago, our embroidery division showed 22% longer turnaround than screen printing despite similar order complexity. I didn't fire anyone--I killed our thread inventory system that required manual counts and changed to auto-reorder scanners. Delivery time equalized within 60 days. The biggest trap is keeping services because "we've always done them." We killed custom patches in 2019 even though they brought $40K annually. They tied up our embroidery machines for small-margin work and caused the bottlenecks I mentioned. Dropping that 2% of revenue freed capacity that let us take corporate uniform contracts worth 10x more. Here's what actually works: pick ONE metric per department that directly connects to profit or customer satisfaction. When that number drops two months in a row, you've found what needs changing. Don't wait for year-end when you're looking at 12 months of damage.
I run BrushTamer, a land clearing operation in Indiana, and we do informal Keep-Kill-Change thinking constantly throughout the season--not just year-end. In land management, weather and equipment downtime force you to evaluate what's working *right now* or you lose profitable windows. The most painful change we made was killing our initial focus on small residential brush jobs. They felt safe and steady, but when I tracked actual profitability per equipment hour, those small jobs were costing us bigger commercial contracts like blueberry orchard removals that could run multiple days on one site. We now say no to anything under a half-day minimum, and our revenue per operating hour jumped enough to add a third team member. One thing I'd add that nobody talks about: **keep your best client relationships even when you kill the service they originally hired you for**. We stopped taking certain small stump grinding jobs, but I personally called those clients to refer them to specialists and explain why. Three of them came back later for full forestry mulching projects worth 10x more because we'd stayed helpful instead of just ghosting them. The biggest mistake is changing something because it *feels* inefficient without tracking whether it actually hurts your bottom line. I almost killed our FAE mulcher attachment thinking skid-steer mulchers were "good enough," but that rare piece of equipment is exactly what wins us specialized blueberry field contracts nobody else can bid on.
I've run these audits for over a decade in home services, and the biggest mistake I see is timing them wrong. We do ours in March/April--our off-season--when technicians aren't slammed with 100-degree emergency calls and actually have mental bandwidth to contribute. Running it in December means you're evaluating systems during your slowest period, which gives you completely skewed data about what's actually broken. Here's what actually works: we track our membership program metrics monthly, but the annual audit focuses on one question--does this process make our techs' jobs easier or harder? Last year, our CRM had 47 different fields techs needed to fill out per job. We killed 31 of them. Our job completion time dropped by 12 minutes per call, which translated to an extra appointment per tech per day. That's real money from a simple kill decision. The "change" category needs hard constraints, or it becomes a wishlist that never gets executed. We limit ourselves to three changes maximum per department per year. When our service department wanted to revamp scheduling, tune-up protocols, AND customer follow-up simultaneously, we made them pick one. They chose scheduling changes, executed it properly, and our same-day service appointments jumped from 60% to 87%. Three half-done changes would've given us nothing. One trap nobody talks about: auditing during growth masks inefficiency. Wright Home Services has been around since 1979, and I've seen companies add revenue while their cost-per-job secretly climbs. We measure our filter replacement upsell rate per tune-up visit--it should stay consistent regardless of how many total jobs we're running. When that percentage drops during busy periods, that's your signal that growth is hiding a process problem, not fixing it.
I've run The Nines Emporium for nearly 10 years, plus another cafe, so I'm constantly fine-tuning what stays and what goes. Here's what I've learned: the audit shouldn't happen once a year--it needs to be baked into how you operate monthly, or you're already too late to fix what's broken. Our biggest win wasn't killing menu items people weren't ordering. It was keeping our core dishes (Bacon Benny is non-negotiable) while changing *when* we introduced specials. We moved from random specials to structured monthly rotations, and it gave our head chef Lani a predictable creative outlet while keeping regulars curious. Sales on specials jumped because customers knew to expect something new, not stumble into it. The trap? Auditing based on gut feeling instead of actual numbers. We thought our loaded shakes were just fun add-ons until we tracked them properly--Fletcher was making 100+ some days. Turns out they were a silent revenue driver we almost overlooked. Now they're a permanent fixture with monthly flavour drops, and we promote them hard on socials. My practical tip: track your top 5 revenue drivers and your top 5 time-drains separately every month. If something's making money but killing your team's energy, that's a "change" candidate, not a kill. If it's doing neither, bin it immediately and don't look back.
I run Rattan Imports, an e-commerce furniture business, and every January I do what I call a "customer journey audit" instead of the typical team review. I track three touchpoints: initial inquiry response time, phone call conversion rate, and repeat customer percentage. Last year our inquiry response was strong but phone conversions were at 34%--we were reaching out but not connecting. The fix wasn't hiring different people or killing the outreach process. I changed when we called. Our older clientele (mostly baby boomers) weren't answering during business hours because they were out. We shifted calls to early evenings and weekends, and conversions jumped to 61% in three months with the exact same team using the same script. The biggest trap in these audits is measuring activity instead of outcomes. We had one employee making twice as many customer contacts as everyone else, but her orders-per-contact was half the team average. Instead of celebrating her effort or killing her role, I shadowed her calls and realized she was rushing to hit contact numbers. We changed her metric from "contacts made" to "questions answered per call" and her conversion rate doubled because she slowed down and actually helped people steer our site. My framework is dead simple: I only audit things customers actually experience, not internal processes they never see. If a customer can't tell the difference, it goes in the "keep" pile automatically. This year I'm looking hard at our product photography turnaround time because customers definitely notice when items aren't properly showcased, even though it's invisible backend work.
I've led a personal injury law firm for 40+ years, and we handle this differently than most--we audit by *case type profitability* and *time-to-resolution*, not just revenue. In 2020, we finded our funeral home negligence cases took 40% longer than auto accidents but generated similar settlements. We didn't kill the practice area; we changed our intake process to screen for stronger liability evidence upfront (photos, police reports, expert availability). That cut our average case duration by 5 months. The trap nobody talks about: **don't audit during crisis**. After Florida's 2023 tort reform (HB 837) slashed our statute of limitations from four years to two, I saw firms panic-kill entire practice areas. We kept ours but changed how we handled them--I personally trained 200+ attorneys statewide on the new timeline requirements. Decisions made under pressure usually need to be re-made six months later. Here's what actually works for professional services: track your team's *energy per matter type*, not just billable hours. We ask our board-certified trial attorneys quarterly: "Which cases energize you, which drain you, and which need a process fix?" One associate hated premises liability--not the work, just our documentation system. We changed the intake form, and her satisfaction jumped. She's still here handling those cases today. Run your audit in February, not December. You need Q4 financials closed and your team rested enough to think strategically, not reactively. We dedicate one full day off-site with zero client interruptions--because if you're fighting fires during the audit, you'll only see smoke.
I run three integrated companies in Florida real estate--brokerage, property management, and construction--so I'm constantly evaluating what's working across different service lines. After 20+ years, I've learned that the "change" category is where the real money lives, not the dramatic kills everyone focuses on. We had loan officers who were great at mortgages but terrible at follow-up communication. Instead of killing that service line, we changed the structure--paired them with our realtors who excel at client touchpoints. Our mortgage-to-closing conversion rate jumped because we kept the technical skill but changed how clients experienced it. That's pure "change" territory paying off. The trap I see constantly: people audit individuals when they should audit processes. When our property management division was bleeding tenant complaints, the knee-jerk was to replace managers. We kept the people, killed the old maintenance request system entirely, and changed our vendor response protocols. Complaints dropped 60% in four months with the same team. My framework is simpler than quarterly reviews--I track one metric monthly for each division: profit per labor hour. When Direct Express Pavers showed strong revenue but weak profit-per-hour, we didn't kill it. We changed our project selection criteria to focus on commercial work over residential. Same crews, better margins, because we audited the work mix, not just the P&L.
I've scaled Capital Energy from launch to 500+ installations across four states in just a couple years, so year-end audits are critical for us. Here's what actually moves the needle: audit timing, not just structure. We run our Keep-Kill-Change review in November instead of December, which gives us 6-8 weeks to implement changes before Q1 momentum hits--waiting until January means you're scrambling while your competition is already executing. The biggest trap we fell into early was auditing based on effort instead of outcome. Our door-to-door setter program looked incredibly busy with high activity numbers, but conversion to actual solar consultations was garbage. We changed the comp structure to reward qualified appointments only, not just door knocks. Same team, but our consultation-to-close rate improved enough that we opened new offices in Vegas and Utah within months. Here's the specific framework: I separate "Keep" decisions into two buckets--"Keep and Scale" versus "Keep but Cap." Our Tesla Powerwall 3 partnership is Keep and Scale because profit per install keeps climbing. But our entry-level sales training program is Keep but Cap--it works, but we learned trying to run it across all four markets simultaneously diluted quality. We kept it, changed it to rotating regional cohorts, and our new rep productivity jumped without killing the program or hiring externally. The data point that matters most in these audits isn't revenue--it's customer acquisition cost per service line. When we tracked CAC for our Enphase inverter installs versus our full solar-plus-battery systems, we realized our marketing spend was backwards. We killed 40% of our generic solar ads and changed our budget toward battery storage education content. Our average project value went up 35% because we were attracting customers ready for premium solutions, not just tire-kickers.
I've run CC&A Strategic Media for 25+ years and helped dozens of organizations restructure their operations, so I've seen these audits go sideways more often than they succeed. The biggest mistake is timing them wrong--most companies wait until December when everyone's mentally checked out and defensive about their performance. We did a mid-January audit in 2018 after I noticed our SEO team was taking 6 weeks to deliver reports that clients needed in 2 weeks. Instead of "killing" the slow performers, I audited our approval chain and found four unnecessary touchpoints. We kept the entire team, killed three approval layers, and changed nothing about the actual work--delivery time dropped to 8 days. Revenue per client jumped 31% that quarter because we could take on more accounts. Here's what actually works: audit your communication friction points first, not your people or even your processes. I map every client touchpoint on a whiteboard and time-stamp them. You'll find 80% of your "change" opportunities hiding in gaps between departments talking to each other. At the Maryland AG's office where I consult, we finded their digital reputation cases were stalling because three different departments were emailing the same client separately--consolidating that into one point person cut case resolution time in half. The psychology matters more than the mechanics. Frame it as "what's making your job harder" instead of "what needs to change" and your team will hand you the audit findings themselves. I've never had to force a "kill" decision when people feel safe identifying what's actually broken.
I run the fitness team at Results Fitness in Alexandria, and we do our Keep-Kill-Change audit in late January--not December. Here's why: after the New Year rush settles (usually around week 3), we can see what actually stuck versus what was just resolution hype. In 2024, we noticed our Tuesday 6pm CXWORX class had only 4-5 regulars despite being a premium Les Mills format. Instead of killing it, we *changed* the time to 5:30pm and attendance tripled within two weeks. The biggest mistake I see fitness teams make is auditing programs in isolation without checking instructor energy levels. Last spring, one of our trainers was crushing it with small group training numbers but told me privately she felt burned out leading the same 6am slot five days a week. We kept the program, killed her Friday session, and changed her schedule to include one evening class. Her retention rate with clients went up 18% over the next quarter because she was genuinely excited to be there again. Track what your team *stops doing naturally* before you force a decision. I noticed our staff gradually stopped promoting our outdoor bootcamp last summer--not because members didn't want it, but because our marketing materials were outdated and embarrassing to share. We changed the collateral and suddenly everyone was talking about it again. Sometimes "kill" decisions are really just "fix the support system" problems in disguise. The 2-for-2 rule I use in progressive overload training applies here too: if something underperforms for two consecutive assessment periods, *then* you have data worth acting on. One bad quarter during a heatwave or staff transition isn't enough to kill a program that took years to build.