Introduction
Welcome back to the weekly newsletter.
Not every tactic deserves more time. Some ideas need patience. Others need to be stopped before they drain energy, money, and attention. The hard part is knowing the difference. This week’s tool is Kill-Switch Criteria: clear “stop or pivot” rules you set before you start, so you do not keep pushing a tactic just because you already invested in it.
Kill-Switch Criteria are simple rules that tell you when to stop, adjust, or continue a tactic. You decide the rules before emotion gets involved. That way, you are not making the call when you feel frustrated, defensive, hopeful, or embarrassed. You make the decision based on evidence.
Weekly highlight: Set clear “stop or pivot” rules for any tactic that’s not performing.
Most people do not quit bad tactics early enough.
They keep running the same approach because they have already spent time on it. They tell themselves it “just needs a bit longer.” Sometimes that is true. But often, the tactic is not working, and the only reason it continues is pride, hope, or habit.
This is how tactical plans become expensive.
You don’t need to quit every slow result. You need a clear rule that separates a slow start from a broken tactic.
That rule must be set before the tactic begins.
What Counts as a Tactic?
A tactic is any specific action you use to create a result at work.
It is not the big goal. It is the method you are testing to reach the goal.
Examples:
- changing the format of your weekly manager update
- testing a new structure for a 1:1 meeting
- using a new approach for stakeholder updates
- trialing a shorter meeting format with clearer decisions
- changing how you prepare for senior leadership meetings
- testing a new process for monthly reporting
- improving how you track and present achievements
- using a new prioritization method for project work
- changing the handover process between teams
- testing a new way to reduce rework or late changes
Each tactic should have three things:
- a target
- a time window
- a stop or pivot rule
Without that, it becomes vague effort. You keep doing it because it feels useful, not because it is clearly working.
Step 1: Define the Result
Before you start, write the result you want.
Not: “Improve communication with my manager.”
Write: “Send one clear weekly update every Friday for 4 weeks and reduce ad hoc follow-up questions.”
Not: “Make meetings better.”
Write: “Reduce recurring meeting time by 20% while still making clear decisions.”
Not: “Be more visible at work.”
Write: “Share one measurable achievement with my manager every week for 6 weeks.”
Not: “Improve reporting.”
Write: “Reduce report preparation time from 3 hours to 2 hours without increasing errors.”
A tactic without a result cannot be judged. It can only be defended.
That is the problem. If the target is vague, you can always convince yourself to keep going. A clear result forces honesty.
Step 2: Set the Review Window
Every tactic needs a fair test window.
Too short, and you quit before the tactic has a chance to work.
Too long, and you waste time on something that should have been changed earlier.
Use a simple guide:
- daily work habit: review after 10–14 days
- weekly manager update: review after 4 weeks
- recurring meeting change: review after 4 weeks
- reporting or process change: review after 1–2 cycles
- stakeholder communication rhythm: review after 4–6 weeks
- learning or skill improvement tactic: review after 4–8 weeks
- larger project tactic: review after one clear milestone
The review window should be long enough to produce evidence, but short enough to prevent drift.
This is especially important in corporate work because bad tactics often survive through habit. Nobody stops to ask if the meeting, report, update, process, or communication rhythm is still useful. It just continues.
A review window forces the question.
Step 3: Choose the Key Metric
Pick one main measure.
Examples:
- meeting time reduced
- number of decisions made
- number of follow-up questions reduced
- report preparation time saved
- error rate reduced
- stakeholder response time improved
- rework reduced
- task completion rate improved
- manager feedback improved
- number of visible achievements shared
Do not track ten metrics. Pick the one that tells you if the tactic is doing its job.
You can still notice supporting data. But the decision should rest on the main metric.
For example, if you test a new weekly manager update, the key metric might be: “fewer clarification questions from my manager.” If you test a new meeting format, the key metric might be: “clear decision made by the end of the meeting.” If you test a new reporting process, the key metric might be: “time saved without quality dropping.”
Simple metric. Clear review. Better decision.
Step 4: Write the Kill-Switch Rule
Now write your rule before you begin.
Use this format:
If [metric] is below [minimum result] by [date], then I will [stop, pivot, or change].
Examples:
- “If the weekly manager update does not reduce follow-up questions after 4 weeks, I will change the format and ask for feedback.”
- “If the new meeting structure does not reduce meeting time by 20% in 4 weeks, we will change the agenda or meeting frequency.”
- “If the new reporting process does not save at least 30 minutes per cycle after 2 cycles, I will review the steps and remove unnecessary checks.”
- “If the stakeholder update rhythm does not reduce last-minute escalations after 6 weeks, I will change the timing or audience.”
- “If the new prioritization method does not help me complete my Top 3 weekly priorities for 3 out of 4 weeks, I will simplify the system.”
- “If my achievement tracking does not give me at least 4 clear examples for my manager update by the end of the month, I will change how I capture wins.”
This removes vague debate.
The rule tells you what to do before emotion gets involved.
Step 5: Decide the Action: Stop, Pivot, or Continue
Your review should produce one of three decisions.
Continue
The tactic is working. Keep going.
For example, your new meeting structure is shorter and decisions are clearer. Your manager update reduces confusion. Your reporting process saves time and keeps quality stable.
That is evidence. Continue.
Pivot
The goal is still right, but the method needs changing.
For example, your weekly update is useful, but it is too long. Your stakeholder rhythm is helping, but the wrong people are included. Your prioritization method works on quiet weeks but collapses when urgent requests arrive.
That does not mean the goal is wrong. It means the method needs adjustment.
Stop
The tactic is not working and does not deserve more time.
For example, a recurring meeting still creates no decisions. A report is still unused. A process adds admin but no value. A new routine creates more friction than clarity.
Stopping is not failure. It is resource protection.
A weak tactic should not be rewarded with more time just because it was started.
Step 6: Watch for False Excuses
Be careful with these lines:
- “It just needs more time.”
- “This is how we have always done it.”
- “People are used to this format.”
- “We already built the template.”
- “Let’s keep it for another month.”
- “It is not perfect, but at least it is something.”
- “The process is annoying but changing it will take effort.”
Sometimes these points are valid. Often, they are comfort dressed as logic.
This is common in corporate work. Old meetings stay in the calendar. Reports keep being produced. Updates keep being sent. Processes keep being followed. Not because they work, but because nobody wants to challenge them.
That is why the kill-switch rule matters.
It keeps the decision tied to evidence.
Step 7: Keep a Short Decision Log
At the end, write three lines:
- What did I test?
- What happened?
- What did I decide?
Example:
- Tested: weekly Friday manager update.
- Result: fewer ad hoc questions, but update was too detailed.
- Decision: keep the rhythm, shorten the format to 5 bullets.
Another example:
- Tested: new meeting agenda with clear decision owner.
- Result: meeting time reduced by 15%, but actions were still unclear.
- Decision: pivot by adding action owner and deadline at the end.
This turns every tactic into learning.
Even a failed tactic gives value if it improves the next one.
Without a decision log, you repeat the same mistake later with a new name.
Application
Before starting your next tactic, write:
- Desired result
- Review date
- Main metric
- Kill-switch rule
- Decision options: continue, pivot, stop
Use this simple format:
If ______ is below ______ by ______, then I will ______.
Do this before you begin. Not when the tactic is already failing.
Summary
Kill-Switch Criteria help you protect time, money, and attention. You define success before you start. You review evidence at the right time. Then you continue, pivot, or stop based on facts; not pride, hope, or sunk cost. Good tactical planning is not only knowing what to do. It is knowing when to stop.
Till Next Time,
Maciej
Build the Life You Were Meant to Live
👉 Are you ready to start?
Begin with Establish Foundations. A free training to help you reclaim your time, energy, and focus, so you can finally start making meaningful progress.
👉 Want to truly change your life and achieve any goal?
Build Life Strategy that’s flexible, achievable, and aligned with what truly matters to you. In just 30 days, you’ll start making real progress toward your goals with tools built to fit your real life.
Take Control of Your Career
Complete blueprint to accelerate your career, salary and change forever the way you look at your career.
👉 Want to learn full framework?
Start with Career Framework. This free training and toolkit help you understand how your career really works, so you can stop guessing, start strategizing, and build a career that actually moves forward.
👉 Ready to re-design your career around your true value?
Step into Career as Product Course. If you're feeling stuck in your role, unsure how to communicate your value, or wondering why others with less experience are advancing faster, this course is for you.
No pressure. Just the tools, structure, and mindset to move forward, wherever you're starting from.
Responses