By Travis J. MacDonald · 20 October 2026 · Updated 6 November 2026
Part 4 of a five-part personal series about burnout, work, and being understood.
1. Burnout at 45 · 2. Being Useful · 3. Distance and Hurt · 4. Process and Work · 5. What the Future Holds
The process. The process. The process. The process.
That's how I sometimes find myself talking when I get frustrated. I want to understand what we're trying to achieve, how the pieces connect, and what would actually make the result better.
A procedure ought to help us do that. When it becomes difficult to explain the purpose of a step, I start asking questions.
An approval should have a reason
Consider a hypothetical small correction to a page. The change itself might be straightforward. That doesn't tell us everything about the consequences of releasing it.
Perhaps the text carries a contractual meaning. Perhaps a shared component affects several pages. Perhaps someone else is preparing a related change. There can be a good reason to check.
I want to understand that reason. What failure are we trying to prevent? What evidence would give us confidence? Who needs to make the decision?
If the same route is used for every change, regardless of its consequences, it deserves examination. Proportionate checking takes judgment. So does knowing when a small change is connected to something bigger.
I could see more than the individual ticket
My instinct is to connect things. A page, a requirement, a change in behaviour: each sits inside a larger system. I think about what depends on it, what it might affect, what someone has assumed, and which edge cases could turn a small omission into a much bigger problem.
Software engineering is something I love partly because of that. I enjoy making the connections and working out a coherent solution.
But the connections aren't necessarily obvious to everyone else. Moving straight to my conclusion can leave people behind. A detailed explanation can leave them struggling to find the point. I have managed both, sometimes in the same conversation.
What helps is being able to work through the problem at the right time, with enough context to make the reasoning useful to someone else.
Where did the original problem go?

A user story is an account of a need. It is worth checking what happened between the original conversation and the description someone is asked to implement.
Who needs this? What are they trying to do? Which questions remain unanswered? Can the person building it ask about the original problem before the proposed solution becomes fixed?
Those questions matter to me because talking is also one way I develop a solution. I can hear a problem and begin working through it aloud before I have a finished idea. Requirements and connections emerge as I speak.
PaperCloak grew through long stretches of dictation like that. What sounds like rambling can be the construction of the system itself.
That creates a real meeting problem. Other people need room to participate. A quick note doesn't reliably preserve a thought I still need to develop, either. Earlier access to the problem and time set aside for exploration can help both needs fit.
A fix is also a conversation
Finding a defect can make the next step feel obvious to the person who found it. There is a failure, and perhaps a repair. Why wouldn't everyone want it fixed?
But the proposed repair still needs examination. Does it address the original problem? What else does it change? What might the person who wrote the original understand that I haven't considered?
I want the same curiosity applied to the failure itself. We should be able to look at what happens, reproduce it and discuss the consequence without making the conversation a judgment of someone's worth.
There is room for care about the person and care about the result. I don't always find the right words for both. I want to get better at that.
Make room for learning
I have always enjoyed helping people understand a system. Explaining something can also reveal where my own understanding is incomplete.
That work takes attention. It belongs in a plan alongside implementation, review and support, rather than being treated as something that happens without using anyone's time.
A useful explanation gives someone more ability to continue independently. It also leaves room for their questions to reveal a better approach than the one I started with.
The interruption can outlast the meeting
When I am following a complicated thought, an interruption can cost more than the minutes it occupies. Finding my way back into the connections can be difficult.
I know the group cannot always stop while I follow every branch. I also know that writing down a few words may not preserve an idea that was still forming.
I need uninterrupted space for that thinking, and other people need a workable way to collaborate with me. Clear expectations about when to explore, when to decide and what needs to be recorded would help.
Making room for the work
The image I return to is a reservoir of connected ideas. A good working arrangement gives those ideas a route into something another person can understand, evaluate and use.
That route includes requirements, questions, experiments, review and the opportunity to discover that an earlier assumption was wrong. It needs to make room for different strengths without asking everyone to work in exactly the same way.
I love building things. I want to understand the need, follow the connections and make the result useful. I also want to keep learning how to bring other people into that process.
That is what I want a procedure to support. If we cannot explain how it helps, we should be able to ask whether there is a better way.
Burnout series: 1. Burnout at 45 · 2. Being Useful · 3. Distance and Hurt · 4. Process and Work · 5. What the Future Holds.
Companion: Getting to Know a Different Kind of Mind.
Artwork from this series
Illustrations exploring restraint, creative freedom, and being understood. These are visual metaphors and include earlier concept variations.
Explore all 31 artwork studies
Study 1 — open larger image
Study 2 — open larger image
Study 3 — open larger image
Study 4 — open larger image
Study 5 — open larger image
Study 6 — open larger image
Study 7 — open larger image
Study 8 — open larger image
Study 9 — open larger image
Study 10 — open larger image
Study 11 — open larger image
Study 12 — open larger image
Study 13 — open larger image
Study 14 — open larger image
Study 15 — open larger image
Study 16 — open larger image
Study 17 — open larger image
Study 18 — open larger image
Study 19 — open larger image
Study 20 — open larger image
Study 21 — open larger image
Study 22 — open larger image
Study 23 — open larger image
Study 24 — open larger image
Study 25 — open larger image
Study 26 — open larger image
Study 27 — open larger image
Study 28 — open larger image
Study 29 — open larger image
Study 30 — open larger image
Study 31 — open larger image