Abraham Lincoln was quoted as saying:
“Give me six hours to chop down a tree and I will spend the first four sharpening the ax.”
What does this have to do with thesis writing?
Just like sharpening the ax represents preparatory work for Lincoln, in problem-solving this translates to properly understanding and framing the problem before jumping to solutions. In the context of thesis writing, understanding and framing are (at least) the Introduction, Context Analysis, and Literature Search sections.
It is tempting to dive straight into “chopping the tree,” especially in a company context where you feel pressure to show results. Although rushing to action without proper preparation might yield quick results, these may not be the most effective, sustainable, or even useful for the company.
The following steps might be helpful when you feel the sharp-vs-chop dilemma:
- Frame the problem: define the problem, understand its context, identify the key factors, and set clear objectives. Skipping or rushing this stage can lead to misdirected efforts or solving the wrong problem.
- Develop a strategy: brainstorm potential solutions, evaluate feasibility, and choose a defensible plan of attack.
- Implement: execute the plan. The better the understanding and planning, the smoother (and faster) the execution.
What to Include in a Context Analysis
A strong context analysis typically includes:
- A clear description of the system/process and stakeholders
- A definition of the key performance indicators (KPIs) and why they matter
- Evidence about the current state (data, charts, bottlenecks, constraints)
- A problem diagnosis that leads naturally to your problem statement and research questions
Being Diplomatic: Don’t Burn Bridges
When writing about a company’s processes, be diplomatic—especially if you are not anonymizing the company name. You can acknowledge challenges without sounding accusatory by focusing on evidence, impact, and improvement opportunities rather than blame. Remember, your company supervisor and stakeholders will likely read your thesis!
Guidelines:
- Prefer neutral, operational language over judgmental adjectives (avoid “messy”, “disorganized”, “outdated”)
- Attribute issues to systems/constraints, not people (“the current workflow” vs “they don’t know what they’re doing”)
- Ground claims in observable evidence (data, logs, lead times, error rates)
- Emphasize intent and collaboration (“opportunities”, “areas to strengthen”, “next steps”)
Tip: Ask ChatGPT or another AI tool to help rephrase critical statements into more diplomatic language.