Software was supposed to make work easier. Instead, people became responsible for coordinating the growing pile of tools surrounding the work itself. We can choose a different standard.
Marcus Hackler8 min read
The work and the system surrounding it have become inseparable. That does not mean the burden should remain with the worker.
Somewhere along the way, doing the work became only part of the job.
Before someone can design, write, plan, analyze, edit, build, or solve, they often have to reconstruct the environment around the work. Find the brief. Check the chat. Search the email. Join the meeting about the message about the file. Update the task. Start the timer. Stop the timer. Explain what changed. Then try to remember where the actual work left off.
None of those activities is meaningless. Organizations need coordination. Leaders need enough information to protect the business, make commitments responsibly, and support the people doing the work. Clients need to understand what they are reviewing and what happens next.
The problem is not that coordination exists. The problem is that we have made each individual personally responsible for carrying it across a fragmented system.
We added tools without designing the system.
Each new tool usually arrived with a reasonable promise. Email would move communication faster. Chat would reduce email. Project software would organize the work. Calendars would protect time. Video meetings would connect distributed teams. Time trackers would make effort visible.
But few of those tools coordinate the whole journey from an intended outcome to completed, reviewed, accepted work. They each hold a piece. The human being in the middle becomes the integration layer.
That hidden role expands with every additional channel. A message creates a meeting. The meeting creates a task. The task requires a file. The file creates feedback. The feedback changes the schedule. The schedule changes the budget. Someone has to carry those consequences from one place to another.
The person became the system because the software never did.
When the system fails, we question the person.
When work slows down, the first instinct is often to ask whether someone is organized enough, focused enough, responsive enough, or accountable enough. That question may occasionally be necessary. But it is rarely the first question a good leader should ask.
The first question should be: what is the context in which this person is working?
Were the outcome and scope clear? Did feedback conflict? Was the person resourced for the work? Did priorities change? Was help requested? Did the work wait on another decision? How much attention was consumed simply keeping the system updated?
Accountability becomes meaningful only when the conditions surrounding the commitment are visible. Without that shared picture, leaders hold opinions while workers assemble a defense from scattered messages, documents, meetings, and memories.
Seven tools do not create one system. They create seven places a person must remember to coordinate.
Software in service is a different standard.
Cards begins with a simple belief: the system should work for people. People should not have to work for the system.
That does not mean software should tell someone how to practice their craft. It should not prescribe how a designer designs, how a strategist thinks, how a writer writes, or how a leader makes a human judgment.
It means the software should carry the operational burden it is capable of carrying. It should keep communication connected to the work. It should preserve what happened without requiring someone to reconstruct the history later. It should route a request to the person responsible for answering it. It should surface the next relevant action. It should track elapsed work automatically instead of demanding constant manual interruption.
The person should bring the skill, judgment, curiosity, and humanity. The system should bring the context, sequence, record, and coordination.
Standards the product can be held against.
01
Protect attention instead of competing for it.
02
Make the next useful action visible without forcing a method.
03
Keep communication contextual to the work and carry its history forward.
04
Let transparency and accountability flow toward workers and leaders.
05
Surface facts and patterns without turning software into a judge of people.
06
Give people their time back—including the freedom to leave work.
The measure is not more activity.
A system serving people is not successful because it produces more clicks, more notifications, more check-ins, or more visible busyness. It is successful when less effort is required to maintain coordination and more attention remains available for the work that matters.
The goal is not to squeeze more output from every minute. If a team planned four hours for a piece of work, the person doing it should have the space to use those four hours well. If they finish earlier, the system should not immediately convert their capability into a reason to tighten the next estimate.
Efficiency should create capacity, learning, resilience, and life—not simply a faster conveyor belt.
A better workday is a human outcome.
The most meaningful result Cards could create is not a prettier dashboard. It is the moment someone realizes: this does not have to be so hard.
They can see what needs their attention. The context is already there. Time is being captured in the background. Questions and feedback return when they are relevant. When the workday ends, they can leave without carrying an invisible queue of administrative obligations home.
What they do with that time is their choice. Practice the craft. Learn something new. Build another career. Spend time with family. Rest. Go outside. Be fully present somewhere that is not work.
That freedom is not separate from the design of work software. It is one of the most important things the design either protects or takes away.
