Build Systems for the Work You Keep Repeating
You’ve been here before.
A vague request from a stakeholder. A production issue flaring up. A meeting that veers off track, leaving everyone a little unclear about what happens next.
And yet you handle it like it’s a brand-new situation.
When you treat recurring challenges as ad hoc, you end up reinventing your way through them. You rethink decisions you’ve already made. You rely on instinct instead of something tested. Some days that works. Other days it doesn’t.
Over time, that inconsistency adds up. It slows you down, creates uneven outcomes, and makes it harder for people to understand how you operate.
To address this, let’s build a system for the daily work that keeps popping up.
The Cost of Starting From Scratch
When you approach familiar work without a consistent approach, the cost shows up quickly.
The first place you feel it is time. You spend energy rebuilding context instead of reusing it. You revisit questions you’ve already answered and rethink approaches you’ve already proven out.
The second place it shows up is in the quality of your work. What you deliver increasingly depends on your current workload or energy level rather than your actual capability. That makes your output harder to trust, even if you are fully capable of doing the work well.
The third impact is less obvious but more important. People don’t know what to expect from you. That uncertainty makes collaboration harder. It creates more follow-ups, more clarification, and more friction than necessary.
You can see this pattern across teams. A significant portion of engineering time is spent on rework, often because expectations weren’t clear or the work wasn’t fully aligned the first time.
Studies estimate that 20 to 40 percent of development effort goes toward rework, and in some cases, it can be even higher. Even before release, teams may end up rewriting over a quarter of their code just to get it into a usable state.
What’s more telling is where that rework comes from. The majority of it isn’t caused by difficult technical problems. It’s driven by inconsistent approaches to defining, communicating, and executing the work. Gaps in requirements alone account for the majority of rework costs.
None of this is caused by a lack of effort. It’s what happens when there isn’t a consistent way to approach the work in the first place.
Defining a “Personal System”
A personal system is a clear, repeatable framework or process you use to tackle work you do often. It typically includes defined steps, reference materials, and a mechanism for adjusting based on feedback or changing circumstances.
Instead of asking “how should I approach this?” every time, you already have a way in. You adjust from there.
|
Where Systems Show Up in Your Work
When you develop systems, it's important to clarify what they look like and how they are perceived by others. Consider three core areas: how you complete work, how you collaborate with others, and how you learn. Let’s dive into each of these categories.
How You Get Work Done
Estimation is a great example.
Without a system, estimates feel like guesses. You’re trying to predict something without a consistent way of breaking it down, which leads to frustration on both sides.
With a system, you approach estimating differently. You break work into pieces, use past experiences as reference points, and adjust as you gain new information. This creates a feedback loop in which estimates improve over time rather than remaining inconsistent. I explore this more in How to Provide Better Software Estimates.
The same pattern shows up in how you define “done.”
If you don’t have a clear approach, work tends to come back. QA finds issues that weren’t considered. Your product owner is requesting changes that you had no idea were even in scope. You end up revisiting work you thought was finished.
A structured approach across planning, development, deployment, and feedback helps close that gap. It reduces rework and ensures that what you deliver holds up after leaving your hands. I broke this down further in When Is Your Work Actually Complete.
|
|
Where can AI save you time?
My friends at Big Creek Growth put together a quick survey to spot the repetitive work you can hand off to automation.
|
|
How You Work With Other People
A lot of the friction in software teams comes from how people interact with each other.
Without a system, communication becomes reactive. You adjust in the moment, which means your approach varies depending on the situation.
In one meeting, you go too deep into technical detail. In another, you leave out context that others needed. When something goes wrong, you respond rather than communicate with intent.
Communication is situational. It depends on context, tone, and audience. I covered this in more detail in The Hidden Communication Skill That Will 10x Your Impact.
You can create simple, repeatable ways of handling common interactions. A consistent structure for status updates. A clear way to raise risks early. A habit of translating technical work into business impact.
These don’t need to be formal or complex. They just need to be consistent enough that people know how you operate.
Trust is built through that consistency. It comes from seeing the same level of clarity, follow-through, and thoughtfulness over time.
That’s the same idea behind winning in the margins. Small actions, done consistently, shape how people experience working with you.
How You Learn and Improve
Growth doesn’t happen automatically.
Without a system, you rely on memory and emotion to guide improvement. You remember parts of what happened, but not the full picture. Feedback fades quickly. Patterns are harder to spot.
That leads to a cycle where you encounter the same problems without fully learning from them.
Reflect on what you intended to do. Gather input from others to understand how it landed. Document what worked and what didn’t. Then translate these insights into improvements for next time.
I outlined a practical approach to this in Need Help With Your Self-Assessment?.
How to Start Building Your First System
You don’t need to overhaul how you work.
Start with something small and repeatable.
Pick one type of work you see often. It could be estimating a project, running a meeting, writing status updates, or handling production issues. The key is that it shows up regularly.
Write down how you approach it today. Capture the steps you actually take when that situation comes up. If it’s not documented, you’ll fall back on memory and repeat the same inconsistencies.
Then refine it.
Look for where things tend to break. Where context gets missed. Where work comes back. Where communication creates confusion. Adjust your approach so the next time is cleaner.
Then use it.
The next time that situation comes up, start from your system rather than from scratch. Follow it, see what holds up, and make small adjustments.
The work doesn’t get easier over time because the problems go away.
It gets easier because you stop treating familiar situations like they’re new.
When you build systems, you reduce the amount of thinking you have to redo. You create consistency in how you show up, how you deliver, and how others experience working with you.
That consistency is what people start to rely on. It’s what builds trust. It’s what allows you to take on more without everything feeling heavier.