Back to Basics
Returning to the Basics Through First-Principles Thinking
Complex problems do not always require complicated solutions. Sometimes, progress begins by stripping the problem back to what is fundamentally true.
When a business problem persists, the natural reaction is often to add something.
Another meeting.Another reporting template.Another approval process.Another software platform.Another round of training.
Adding something creates a visible sense of action. It reassures us that the problem is being addressed.
But complexity can also hide the fact that the organisation has not answered the most basic questions:
What are we actually trying to achieve?
What is really causing the problem?
What information is essential?
Who is responsible for acting?
What is the simplest way to make the desired outcome happen consistently?
Until these questions are answered, adding more layers may make the business look organised without making the situation clearer.
Complexity Can Create an Illusion of Sophistication
A detailed system can appear more professional than a simple one. A long report can appear more thorough than a short one. A complicated framework can appear more credible than a few direct questions.
But sophistication is not measured by how much has been added.
It is measured by whether people understand what needs to happen and can act on it effectively.
When a process contains too many steps, people may remember only some of them. When reports request too much information, employees may complete them without understanding what management actually needs. When responsibilities are divided across too many roles, nobody is certain who owns the final outcome.
The organisation gains activity—but loses clarity.
Simplicity does not mean removing everything. It means removing what does not contribute meaningfully to the intended result.
Going Back to Basics Is Not Going Backwards
Returning to the basics can sometimes feel unsophisticated, especially after a company has invested in systems, processes or technology.
But the basics are what allow everything else to work.
Before improving a reporting system, employees must understand:
what needs to be reported;
when it must be reported;
who needs the information;
what action the information should trigger;
who is responsible for following up.
Before introducing a new sales framework, the team must still understand:
who the right client is;
what problem the client is trying to solve;
how that problem is currently affecting them;
why the proposed solution is relevant;
what the agreed next step should be.
A sophisticated tool cannot compensate for unclear fundamentals.
Going back to basics is not about rejecting progress. It is about ensuring that progress is built on something solid.
What Is First-Principles Thinking?
First-principles thinking means breaking a problem down into its most fundamental facts and requirements, then rebuilding the solution from that foundation.
Instead of asking:
“How do other companies do this?”
We begin by asking:
“What must be true for this to work?”
Instead of accepting:
“This is how we have always done it.”
We ask:
“Why does this step exist, and does it still serve the intended outcome?”
Instead of immediately searching for a better system, we first clarify the problem the system must solve.
This helps us separate what is genuinely necessary from what has been inherited, assumed or copied from somewhere else.
A Simple Operational Example
Imagine an SME experiencing repeated delays because site problems are not reported early enough.
The immediate response may be to introduce a new reporting application, daily submission requirements and a more detailed escalation form.
But first-principles thinking begins with the fundamental outcome:
The right decision-maker must receive enough information to act before the issue causes avoidable delay or cost.
From there, the company can ask:
What types of problems require escalation?
How quickly must each type be reported?
What minimum information does the decision-maker need?
Who must receive it?
What happens after the report is submitted?
What is preventing employees from reporting earlier?
The answer may involve a digital system. It may also involve a simple escalation guide, clearer authority limits and a short standard reporting format.
The correct solution should emerge from the actual requirement—not from a preference for a particular tool.
A Simple Sales Example
Suppose a sales team is experiencing weak conversion.
Management may respond by adding scripts, presentations, incentives, CRM requirements and another closing workshop.
But the team should first return to the fundamentals:
Are salespeople speaking to suitable prospects?
Do they understand the client’s actual concern?
Are they asking enough questions before presenting?
Is the recommendation relevant to what was discovered?
Has a clear next step been agreed?
Is follow-up happening consistently?
The conversion problem may not require another closing technique.
The team may simply be presenting too early, misunderstanding client concerns or failing to establish a meaningful next step.
Returning to the basics makes the real development need more visible.
Why Simplicity Improves Behaviour
A system only works when people can understand and use it consistently.
When expectations are simple and clear:
employees know what matters;
responsibility becomes easier to identify;
decisions can be made more quickly;
mistakes become easier to trace;
managers can provide more focused feedback;
progress becomes easier to measure.
When the desired behaviour requires employees to remember too many steps, consult several documents or update multiple systems, workarounds become more likely.
This is not always because employees resist accountability. Sometimes the environment makes the correct behaviour unnecessarily difficult.
A practical system should make the right action easier to understand and perform.
Simplicity Is Not the Same as Oversimplification
There is an important distinction.
Some business problems are genuinely complex. They may involve regulatory requirements, safety controls, financial risks, multiple stakeholders or complicated technical work.
These issues should not be reduced carelessly.
Simplicity does not mean pretending that complexity does not exist. It means organising complexity so that people can understand:
what matters most;
what decision must be made;
what action is required;
who owns the next step.
The goal is not to remove necessary controls. It is to ensure that every layer has a clear purpose.
Complexity should be justified by genuine operational needs—not by habit, fear or the desire to appear sophisticated.
Simplicity Requires More Thinking, Not Less
Complicated solutions are sometimes easier to create because they allow us to include everything.
Simplicity requires harder choices.
We must decide what is essential, what can be removed and what the business is genuinely trying to accomplish. We must question familiar practices and accept that some existing activities may no longer provide meaningful value.
That can be uncomfortable.
A shorter report requires management to decide which information actually matters. A clearer process requires somebody to accept ownership. A simpler system makes gaps and inconsistencies more visible.
Complexity can allow responsibility to hide. Simplicity exposes it.
Five Questions to Return to the Basics
When a problem becomes confusing, begin with five questions:
1. What outcome are we trying to achieve?
Define the result clearly before discussing the solution.
2. What do we know to be true?
Separate observable facts and evidence from assumptions or opinions.
3. What is essential for the outcome to happen?
Identify the minimum information, actions, resources and responsibilities required.
4. What is making the correct action difficult?
Examine the process, working environment, capability and leadership conditions.
5. What is the smallest practical change we can test?
Implement a focused improvement, observe the result and add further structure only when necessary.
Clarity Creates Better Decisions
When people understand the purpose, priorities and next action, they can make better decisions with greater confidence.
This is why simplicity matters.
It reduces noise, exposes assumptions and returns attention to the result the business is trying to achieve.
The strongest solution is not always the most advanced or comprehensive one. It is the solution that addresses the real problem, can be understood by the people involved and can be sustained in daily practice.
Before adding more, return to the basics. Understand what must be true, remove what does not serve it and rebuild from there.
This principle sits at the heart of Evolv’s advisory approach: simplify the challenge, clarify what matters and introduce practical changes that people can sustain.
Comments