About

I'm Tivon.

I use SQL, Python, and applied analytics to work through real business questions.

My background started in finance and accounting, which shaped how I approach analysis. I learned early that small details can make a big difference, so I tend to start with practical questions. What is being measured? Do the numbers line up? What assumptions are built in? And what do the results actually support?

Over time, my work expanded into customer, operational, financial, and market data. On this site, I break down that process in plain language by showing how I frame the question, check the data, structure the analysis, and explain what the results do and do not show.

Tivon Johnson

Applied analytics and data science for business decisions

Github Linkedin Medium

How I approach analytics

  • Start with the business question, even when it's unclear
  • Identify what data is available and what isn't
  • Define what the analysis needs to measure or detect before adding complexity
  • Make assumptions explicit instead of pretending the data is perfect
  • Use the right tools to get a useful answer
  • Be honest about uncertainty, tradeoffs, and next steps

The goal is analysis that is solid enough to support real decisions.

You won’t find theory for its own sake here. If I cover modeling, it will be tied to a specific business question and the decision it supports.

Why this site exists

This site is where I document how I think through business problems, deepen my understanding of analytics and data science, and share patterns and ideas that hold up outside of textbooks. Writing things out forces clarity. Clarity is what good analysis depends on.

What you can expect

  • Clear explanations that get to the point
  • Examples drawn from real situations
  • Emphasis on understanding the reasoning behind each step
  • Practical guidance you can apply immediately

Links

GitHub → SQL + Python walkthroughs and supporting files
LinkedIn → professional background
Medium → cross-posted articles and broader analytics writing

Feedback welcome

I’m always refining these posts. If you spot an error, a clearer explanation, or a better way to do something, just reply to any newsletter email.

If you are not subscribed, use LinkedIn to send a note.

Start here