DAY 5 | The Honest Truths and the Roadmap Five days ago, I told you I have a Master's in software technology, cannot code, and broke into business analysis anyway. Here is the whole way in, on one page, and the part nobody says out loud. This week walked through what the role really is, the experience you are already carrying, and the practical path to a first job. Today I want to leave you with two things: the honest truths I wish someone had told me at the start, and a sim

DAY 4 | The Practical Path In - How to break the experience catch-22 and get your first role There is a catch-22 that traps almost everyone trying to break into this field: you need experience to get the job, and the job to get the experience. I stood in the middle of that loop once, qualified on paper and stuck in practice, wondering how anyone ever gets through the door. Here is what I learned climbing out of it, and what I now tell everyone I mentor. You do not break the

DAY 3 | The experience you already carry, in the language of this job The most common thing people say to me when they want to break into this field is that they have no relevant experience. It is almost always false. The fear behind it is real, so I want to take it seriously rather than wave it away. When you are looking in from the outside, everyone already inside seems to speak a language you do not, and it is easy to conclude you are starting from nothing. But the premis

DAY 2 | What a Business Analyst Actually Does - The most misunderstood role in tech, explained plainly Most people trying to become a business analyst cannot actually describe what one does, and that is not their fault. It is one of the most misunderstood roles in the whole of tech. The title comes in a hundred versions: business analyst, systems analyst, product analyst, functional analyst, and the job descriptions are so vague they could mean almost anything. So people pic

DAY 1 | How I broke into business analysis without being a developer I have a Master's in software technology, and I cannot code. I trained as a computer engineer at Covenant University in Nigeria, then moved to Aberdeen for a Master's in software technology, finishing around 2011. On paper, I was headed straight for a developer's desk. And somewhere in the middle of all that study, I had to admit something that felt, at the time, like a quiet kind of failure. I did not have

DAY 5 | The Whole Path, and How to Climb It - The transitions, the plateaus, and a way to place yourself The whole path comes down to one idea: at every stage, moving up means letting go of the thing that made you good at the stage before. Here is the map on one page. A career map is not there to tell you something new each time you look at it. It is there to help you see where you actually are, and what to build next, on the days you feel stuck without knowing why. So before

DAY 4 | The Consultant: Selling Judgment, Not Hours - The independent expert, and what changes when you sell judgment The consultant is a different animal from everything that came before. You are no longer inside one organisation climbing a ladder. You are an outside expert, hired for judgement and perspective across many. This stage takes two broad forms, and the shift underneath them is the same. There is the internal principal or expert consultant, who has gone so deep th

DAY 3 | The Lead Analyst: From Doing to Multiplying - When your value stops being your own output The move from senior to lead BA is the hardest transition on the whole path, because it asks you to give up the very thing that got you here: being the person who does the best work. Up to this point, every stage rewarded you for what you personally produced. The junior BA is rewarded for reliable output, the senior BA for owning hard outcomes. Both are about your own hands. The

DAY 2 | The Senior Analyst: From Executing to Owning - The leap from doing the work to owning the outcome The leap from junior BA to senior BA is not more of the same work done faster. It is a change in kind, from executing tasks to owning outcomes, and it is the transition that most defines a career. Yesterday's stage was about becoming reliable at the defined work. This stage is about what happens when the work stops being defined. Somewhere along the path, the tasks handed

DAY 1 | The Junior Analyst: Learning to Be Useful - The whole path, and why the first job is to be reliable A business analyst career is not one job you slowly get better at. It is four different jobs wearing the same title, and most careers stall because nobody says so out loud. We tend to picture a career as a single climb: you start knowing a little, you learn more, you get faster and more confident, and one day you are senior. That picture is wrong in a way that quietly t

DAY 4 | Speaking to the Person Who Has to Decide - Tailoring the story to the executive who must act on it The same story has to be re-cut for the person who has to act on it, because a decision-maker is not a smaller version of your team. They are a different audience with a different need. You can have a true finding, the right narrative shape, and clear, concrete data, and still lose the decision if you deliver it as though the executive has the time and context of someone

DAY 3 | Numbers Don't Speak for Themselves - Turning data into meaning that an executive can feel A number is not an insight. It is the raw material an insight is made from, and the gap between the two is where most data presentations quietly fail. This week has been about turning analysis into a story people act on, and today we face the hardest raw material of all: the numbers themselves. This is where the recent work on reading and interpreting data meets the work of commu

DAY 2 | Every Case Is a Story With Three Parts - The narrative shape that turns a report into a decision A report lists. A story moves. The entire difference between them is structure, and the structure is simpler than you think. Yesterday I argued that people act on stories, not data. That can sound like vague advice, the kind that is easy to nod at and impossible to use. So today is the practical shape, the actual skeleton of a case that moves someone to a decision. It is n

DAY 1 | Why correct, careful analysis so often changes nothing The hardest thing to accept about good analysis is that being right is not enough. It is not even most of the job. A few weeks ago this series worked through how to get the numbers right: reading data honestly, interpreting it without fooling yourself, turning it into a decision you could defend. That is the hard, unglamorous craft, and it matters. But there is a second half that almost nobody teaches, and it is w

DAY 5 | The Clear-Thinking Toolkit - The whole week on one page, and the case for judgment as your edge Clear thinking is not four separate skills. It is one habit, distrusting your own certainty long enough to check it, wearing four different faces. Here is the week on one page. A toolkit is not there to teach you something new each time you open it. It is there to hold the good habits steady on the days you are rushed, sure of yourself, and under pressure to just decide. So

DAY 4 | Tools That Sharpen Judgment - A small kit of reasoning moves that make you right more often You cannot make yourself smarter on demand. But you can run a decision through a shape that catches the things your confidence is hiding, and that is most of what good judgement actually is. This week has been about seeing clearly: catching your own bias, checking the frame, testing the evidence. Today is the practical kit, a small set of reasoning moves you can apply deliberat

DAY 3 | Testing the assumptions and evidence under a confident conclusion Behind every confident conclusion sits a chain of small inferences that nobody checked, and if one link is weak the whole conclusion is too. So far this week we have worked on catching bias in how you judge, and on the frame you put around a problem. Today we go to the join between them: the moment a pile of raw facts turns into a belief you will act on. That turn happens so fast it feels like observati

DAY 2 | How the way you state a problem controls the answers you can see The frame you put around a problem decides, before anyone says a word about solutions, which solutions are even thinkable. This is the most powerful idea in the week and the least noticed, because framing happens so early and so quietly that it feels like description rather than choice. When you state a problem, you are not just reporting it. You are drawing a boundary around it, deciding what is inside

DAY 1 | Why capable, experienced people get confidently wrong You cannot think your way out of a bias you do not believe you have. That is what makes bias the hardest problem in this whole series, and the right place to begin. We tend to imagine that clear thinking is something you either have or you do not, and that careful, intelligent people mostly have it. The uncomfortable truth is that intelligence offers almost no protection. The mind runs a set of fast, automatic shor

DAY 5 | Your Influence Playbook: The whole week on one page, and one scenario that ties it together Influence without authority comes down to three things: get heard, build trust, and move the decision. Here is the week on one page. A playbook is not there to teach you something new each time you open it. It is there to hold the good habits steady on the days you are rushed, outranked, or talking to a room that has every right to ignore you. So before the worked example, here