> rules from the workshop wall
Principles
Less Miserable Tech starts from a simple belief:
Technology should reduce friction, not create new rituals of suffering.
These are the principles I keep coming back to while working with real businesses, real people, messy workflows, and tools that are usually more complicated than the problem required.
They are not commandments. They are workshop rules. If a tool, AI assistant, website, plugin, workflow, or automation makes these harder, something has gone sideways.
Name the friction before choosing the tool.
If you cannot clearly name the friction, you are probably not ready to pick the tool.
A lot of technology projects start with the visible symptom: “we need a new system,” “we need AI,” “we need automation,” “we need a plugin,” “we need a dashboard.”
Maybe.
But first: what is actually painful?
Is the work being re-entered? Is the decision being remade every time? Is someone hunting for the same document over and over? Is the system expecting a person to remember something the system should remember?
The tool comes later. The friction comes first.
Build the smallest useful fix.
Do not build the whole cockpit when one repeated path needs to be smoother.
The best fix is often smaller than the first idea. A better default. A shorter path. A checklist. A tiny automation. A clearer intake form. A way to stop retyping the same thing.
Small does not mean trivial.
Small means it can actually land, be used, and reduce pain before everyone forgets why the project started.
AI needs business context.
Useful AI needs the work, the person, and the definition of success.
The real problem with AI is not usually that people picked the wrong magic prompt. The real problem is that the system does not know the business yet.
It does not know the documents, the workflow, the customer, the exceptions, the tone, the constraints, or what “done” means.
AI gets useful when it has context. Otherwise, it is just a very confident stranger with a keyboard.
Trust is built through repeated friction reduction.
Trust is not created by sounding intelligent. It is created by reducing uncertainty repeatedly.
People trust systems that help them finish real work, avoid mistakes, and feel less lost the next time.
That trust usually grows through small wins:
- the right information appears when needed
- the next step is obvious
- the repeated task gets easier
- the scary part becomes routine
- the system remembers what the person should not have to
Trust is cumulative. So is misery.
Choose carefully.
Leave working things alone.
Not every system needs to be replaced, automated, or improved. If it is not causing real friction, or the fix costs more than the pain, leave it alone and spend your energy where it matters.
Sometimes the least miserable tech decision is to not touch the thing that already works.
If the fix costs more than the pain, it is not a fix. If automation makes the rare case easier but the common path harder, it is not progress. If the new tool creates more rituals than it removes, congratulations: you have invented a fancier problem.
Improve the parts that hurt. Respect the parts that do not.
Build the net for the river you’re already standing in.
Do not confuse a passing idea with a scarce idea. If you are standing in the flow, build the net.
Good observations show up while you are doing the work: in meetings, in the truck, on the patio, at the office, in the middle of a messy workflow that refuses to behave.
The point is not to catch every fish by hand.
The point is to build a better net for the river you are already standing in.
For Less Miserable Tech, that means the work is not just having good ideas. The work is building a capture-and-processing system:
- notice the signal
- preserve enough raw context
- extract the useful nugget
- do the public-safety pass
- shape it into a post, field note, audio segment, or principle
- publish consistently when ready
A less-miserable system helps the human trust the flow because it catches enough of the good material to work with later.
Hide the plumbing.
The tool is not ready for normal people until the plumbing disappears.
A useful technology system may have complicated machinery underneath: servers, profiles, memory stores, archives, providers, gateways, voice models, tools, logs, sync jobs, and admin workflows.
That complexity can be real. Sometimes it is necessary.
But the user should not have to understand it to receive value.
For normal people - smart, capable, wise people who are not trying to become systems engineers - the system should feel like a calm, personal, useful front door.
The advanced system can still exist under the floorboards. But the person using it should know:
- what to say
- how to stop it
- what it heard
- how to correct it
- how to ask for simpler help
- whether the system needs something from them
Power can live in the basement. The human should get the living room.
put it to work
The principles are useful only if they change what you build next.
Start with one real workflow. Name the friction. Make one part less miserable. Then do it again.
Start with Week 1