Measure
Capture what is happening through telemetry, field data, analytics, and observation.
Technical founder · performance engineer · systems builder
I’m Kanmi Obasa. I build measurement systems, simulations, civic infrastructure, developer tools, and digital products that make complex behaviour measurable, testable, understandable, and actionable.
The through-line
Across performance engineering, simulations, civic technology, and products, the work is to observe what is happening, represent it clearly, and test what to do next.
Capture what is happening through telemetry, field data, analytics, and observation.
Represent behaviour with software, simulations, experiments, and structured systems.
Turn signals into explanations, trade-offs, and useful intelligence.
Build interventions and products, then measure what happened.
Current work
A systems and simulation company with a current commercial focus on performance engineering for revenue-critical digital experiences.
An alpha Nigeria city-building and civic simulation built on Govern, modelling neighbourhoods, public services, resources, and trade-offs. Its mechanics and presentation are still evolving.
An editorial experiment combining browser behaviour, diagnostics, and storytelling. The browser is the patient, websites are the experiences it recounts, and drafts are reviewed before publication.
Public civic information and infrastructure that help people inspect representation, legislation, and governance.
A long-running Nigerian-Canadian community platform for practical resources, businesses, professionals, events, and connections.
An experimental decision-support concept for organizing evidence, current conditions, uncertainty, and possible actions. It is not deployed institutional infrastructure.
Engineering practice
Measure real behaviour, locate constraints, change the system, then verify the result. That discipline connects web performance work to the simulations, developer infrastructure, and decision systems I build.
Industry work remains unnamed where it is confidential. The public work here describes projects and tools without claiming unverified outcomes.
How I work
Understand the goal, the system, and the constraints before treating code as the answer.
Separate what is known from what is assumed. Make the quality of the evidence visible.
Find the pattern, investigate the anomaly, and translate technical signals into the language of the decision.
Act when confidence is sufficient, measure what happens, and update the model.
Journey
My path has moved through computer science, independent products, performance engineering, reliability, analytics, civic infrastructure, and simulation.
The recurring work is to understand how a system behaves, identify what matters, and build a way to test what should change.
Read the journeyCurrent direction
Current work spans TraceLayer's performance and systems-intelligence practice, NigSim, TraceLayer Lab's Browserapy experiment, civic information, community infrastructure, and experimental decision systems.
Latest writing
Why user-focused performance measurement matters more than convenient metrics.
A concise guide to turning Chrome User Experience data into useful performance decisions.
Need help with a revenue-critical digital system? TraceLayer handles performance engineering enquiries.
Interested in products, simulations, civic work, research, or writing? Contact Kanmi directly.