4of 7
Effectiveness before efficiency: review work as a founder
Before optimising a workflow, check that it serves the right goal. Regularly reviewing your priorities can reveal work that no longer needs to be done at all.
Adapted by the EWOR Team from 2 sources 3 min read
Speed does not rescue the wrong direction
You can automate a process and measure every step without questioning whether the work needs to happen at all. Daniel Dippold, CEO and co-founder of EWOR, draws a useful distinction: effectiveness means choosing work that advances your objective; efficiency means doing that work well. Before improving how a task is done, make sure it is worth doing in the first place.
Good execution still matters. Give it work worth executing.
Write the objective above the task list
Before reviewing activities, state the outcome the company or team is trying to create in the current period. If the objective is vague, efficiency metrics will fill the vacuum.
For every major activity, complete the sentence:
We do [activity] because it should change [outcome] through [mechanism].
Then label the evidence: observed, inferred or assumed. A task with no credible mechanism may be stopped. A task with a plausible but untested mechanism belongs in an experiment. A task with repeated evidence can enter an efficiency loop.
Urgency is not the same as effectiveness. A request can require a fast response and still deserve a later review of why it keeps appearing.
Make time to review direction
Reserve a regular time to step back from delivery. Daniel suggests a weekly review; choose a duration and cadence that lets you examine direction without turning it into another ritual.
Use the review to ask:
- What outcome changed this week?
- Which activities plausibly caused that change?
- What consumed effort without advancing the objective?
- Which assumption became weaker or stronger?
- What should stop, start or remain stable?
- Which small set of priorities deserves protected capacity next week?
Choose few enough priorities to guide real trade-offs. Five is the source’s suggested starting point, not a number the team has to obey.
Review the day without scoring every minute
At the end of the day, choose a few substantial tasks and ask “why?” until the connection to the objective is explicit. Do not turn this into a percentage score or an expectation that every minute maps directly to a metric. Maintenance, recovery, relationship work and discovery may be necessary even when their effect is indirect.
The purpose is to expose patterns:
- Reactive work repeatedly displacing a strategic priority;
- Optimisation of a channel or product path that has not earned continued investment;
- Recurring manual work that can be removed or delegated;
- Important work avoided because its output is uncertain or uncomfortable.
Separate a task’s value from how satisfying it feels to complete.
Optimise only after the keep decision
Once an activity survives the effectiveness review, improve it. Batch similar work, protect focused time, automate repetition, clarify ownership or redesign the interface between people. Measure whether the change preserves quality while reducing time, cost, delay or error.
Tools are implementation choices, not the system itself. A new task manager cannot decide whether the task matters.
Decide when to stop or reconsider
Every recurring initiative needs a trigger for reconsideration: no movement in the intended outcome, a changed assumption, unacceptable cost, or a better route discovered elsewhere. Without a stop rule, yesterday’s effective work becomes today’s ritual.
Choose the work, improve how you do it, then check the result. When the evidence changes, reopen the choice. The aim is not to do less for its own sake; it is to stop spending effort making the wrong work faster.
Sources:





No comments yet.
Be the first to comment on this signal.