Methods · The working approach
Start with a question.
Make it useful.
The tools change between a website, a financial model and a machine-learning study. The habits carry across: understand the task, look closely at the evidence and make the result something another person can use and question.
Find the decision behind the request.
The work starts with a practical task. A site map might support a shortlist; a document tool might make a review easier. Being clear about that job helps define a useful first version.
A specific question, a user and a way to judge the result.
Get close to the source material.
Source review looks for coverage gaps, inconsistent definitions and examples that do not fit. That might mean reading a report, inspecting a workbook or checking what a sensor actually recorded. These details often change the approach.
A source register, a data check or a small working example.
Make the judgement calls visible.
Some inputs are measured; others are estimates or choices. Keeping them distinct makes it possible to explore how an assumption changes the answer. A model is easier to use when someone can see where their judgement belongs.
Named assumptions, a baseline and useful comparisons.
Build a way to question the result.
The checks fit the work: a comparison with an existing workbook, an evaluation on held-out sessions or a reviewer inspecting the source behind an extracted field. A convincing demo is the start of that process.
Checks and review steps that match the claim being made.
Leave something useful behind.
The output needs to fit the next step. Sometimes that is an editable application, sometimes a spreadsheet or a clearly sourced report. Documented decisions and known limits make the work easier to pick up again.
A usable result with enough context to maintain and improve it.
A few useful distinctions
Small words can
change the claim.
Clear descriptions distinguish what a system does, what a study found and what remains on the development roadmap.
Built, tested and validated
A feature can be implemented before its performance is well understood. Tests establish something about the cases they cover. Validation needs a clear basis and setting. Naming the stage helps a reader assess a working prototype on its own terms.
Ichne’s current research stageRecorded values and modelled estimates
A staffing estimate is different from a recorded headcount. A scenario is different from a forecast. Keeping the source and assumptions visible helps prevent a useful approximation from becoming a fact by repetition.
How the workforce model handles thisA promising result and a transferable one
A result on a public dataset or a short backtest can help choose the next experiment. It does not establish performance in a new workplace or market. The evaluation setting stays close to the claim, including results that challenge the approach.
The local vision evaluation studyThe result should fit the job
Different forms.
The same care.
- 01 · Software
Something you can keep working in.
Clear interactions, editable outputs and a way to recover from changes.
Explore Aphelion - 02 · Models
Something you can compare and challenge.
Visible assumptions, useful scenarios and outputs that fit a review.
Explore cost modelling - 03 · Research
Something you can follow back to the source.
A clear question, careful definitions and evidence kept close to the explanation.
Explore the research method
Have a question in mind?
Start with what the work needs to do.
A little context about the task is a good place to start.