Evidence and assumptions
Findings should say what was reviewed, what the evidence supports, and what could not be verified. Missing information is a constraint to record, rather than a gap to fill with certainty.
ABOUT E-GEIST
A practical approach to technical decisions.
“We Keep IT Simple” is the principle behind the e-Geist approach: explain how the systems work, make the choices understandable, and leave useful documentation for the people who need to act.
e-Geist
We Keep
IT Simple.
Work from the situation you actually have.
A technical recommendation has to account for existing systems, dependencies, and the people who will maintain the result. A new tool may be appropriate; a configuration change, a clearer procedure, or better documentation may be enough. The assessment should explain the reasoning.
IT Consulting addresses technology choices and architecture. Cyber Security Intelligence connects exposure, threats, and business risk with security priorities. IT Systems & Infrastructure covers the administration and evolution of Windows, Linux, and mixed environments. These areas meet in everyday decisions, while keeping their objectives distinct.
WORKING PRINCIPLES
What makes a recommendation useful.
Choices with trade-offs
Compare options against the needs of the organisation. Explain the maintenance effort, operational implications, and dependencies as well as the expected benefit.
A usable handover
Conclusions need to be useful after the discussion. Priorities, procedures, and open questions should be clear enough for the responsible people to plan the next steps.
HOW AN ENGAGEMENT WORKS
Agree the question. Define the work.
The first discussion establishes the problem and the decision it needs to support. Scope, access, responsibilities, and expected outputs belong in the proposal, before technical work begins.
- 01
Define the scope
Identify the systems or decisions involved, the information available, and any operational constraints. Agree what is included, what is excluded, and who provides access or approval.
- 02
Assess and discuss
Review the agreed information, explain the findings, and compare possible actions. Separate evidence from assumptions, and discuss the implications with the people responsible for the systems.
- 03
Document the next steps
Bring the conclusions together in the agreed format: findings, options, priorities, or operating guidance. Record dependencies, responsibilities, and any validation that remains outstanding.
START THE DISCUSSION
What needs a closer look in your IT?
Describe the issue, the systems involved, and the decision you need to make. General information is enough to begin.