Skip to content
Kuza Ndoto Academy

Launch Your Career

Prove your skills and test your ideas before anyone else does

Personal Development4 chaptersAbout 26 min read

Build a portfolio that gets you hired and validate a business idea in two weeks, two ways to create your own opportunities.

By Kuza Ndoto Editorial

Chapter 1

Before you begin: creating your own opportunities

Many young people are told to wait. Wait for the job advert, the interview call, the investor, the right moment. Waiting feels safe, but it hands control of your future to other people. This book is about a different approach: creating your own opportunities by producing evidence. Whether you want a job or want to build a business, the people who move first are usually the ones who stop describing what they could do and start showing it.

Who this book is for, and the problem it solves

This book is for students, recent graduates and early-career professionals in Kenya and East Africa who feel stuck at the starting line. You might be applying for graduate roles and hearing "we need someone with experience". You might have a business idea you have been thinking about for months but have not tested. You might want both: a job now and a venture on the side.

These look like two different problems, but they share a root. In both cases, someone needs to take a risk on you. An employer is risking a salary on a hire. A customer is risking money on a product. And in both cases, the same thing reduces that risk: real evidence that you can deliver value. Without evidence, you are asking people to trust your claims. With it, the decision becomes much easier.

The big idea: evidence beats promises

Every chapter of this book applies one principle. Do not ask people to believe you. Show them, and let their behaviour show you.

  • For a career, evidence means a portfolio: small, real projects that prove you can do the tasks a job requires, before anyone has given you the title.
  • For a business, evidence means validation: tests with real customers that show whether they will act and pay, before you spend months building.

The two skills reinforce each other. Building a portfolio teaches you to work backwards from what employers actually need. Validating an idea teaches you to work backwards from what customers actually do. Both train the habit of testing your assumptions against reality, which is one of the most valuable professional habits you can have.

Key idea

Employers hire evidence and customers pay for value they believe in. In both cases, small, finished, real-world proof is worth more than any amount of polished description. You can start creating that proof this week, without anyone's permission.

A guided tour of the chapters

Building a Portfolio That Gets You Hired, Even With No Experience

The first chapter shows you how to break the "no experience" loop. You will learn to collect real job adverts, list the tasks that recur and design small projects that mirror them. You will see project ideas across software, data, design, marketing, finance and writing, and learn to document each project as a short case study in four parts: problem, approach, result and what you learned. Finally, you will turn each project into a strong CV line and a STAR interview story (Situation, Task, Action, Result). Afterwards, you will be able to plan, finish and present your first portfolio project.

Validate Before You Build: Testing a Business Idea in Two Weeks

The second chapter shows you how to test an idea cheaply before investing heavily. You will learn to work in the order problem, customer, solution; to write falsifiable assumptions with pass and fail marks set in advance; and to run customer discovery interviews that ask about past behaviour instead of hypothetical opinions. You will then design smoke tests, such as a landing page, pre-orders or a WhatsApp catalogue, build a minimum viable product, and use Eric Ries's build–measure–learn loop. Afterwards, you will be able to run a two-week validation and decide with evidence whether to persevere, pivot or stop.

Your 30-day launch plan

The closing chapter combines both chapters into a four-week plan. You will finish a portfolio project and run a full validation test, so that by day 30 you have real proof to show employers and real evidence about your idea.

How to get the most from this book

Read both chapters, even if you are only interested in one path right now. Job-seekers gain a lot from thinking like a founder: understanding customers is valuable in any role. Founders gain from thinking like a job-seeker: documenting work clearly makes you more credible to partners, customers and funders. And a well-documented validation test makes an excellent portfolio case study in its own right.

Do the exercises as you read, not afterwards. When the portfolio chapter asks you to open three job adverts, open them. When the validation chapter asks you to write assumptions, write yours. The book is designed to produce something real, not just understanding.

Keep a launch notebook. Use it to record job tasks, project ideas, interview notes, assumptions and results. Write things down the same day, while details are fresh. Those notes will become your case studies, CV lines and decision records.

Try this

Before you read on, write two lines in your launch notebook. First: the job title you want within a year. Second: one problem you have noticed that people around you would pay to solve. You will build on both throughout the book.

Above all, aim for finished rather than perfect. A small project you complete and explain well beats an impressive one that stays half-built. The same is true of validation tests. Progress comes from finishing and learning, then going again.

Chapter 2

Building a Portfolio That Gets You Hired, Even With No Experience

Employers hire evidence. How to create proof of your skills before anyone gives you a job title.

"We need someone with experience." If you have heard that line, you know the trap: you cannot get experience without a job, and you cannot get a job without experience. A portfolio is how you break the loop. It is a small collection of real work that proves you can do what an employer needs, before anyone has given you the title. This article shows you how to choose the right projects, document them properly and turn them into CV lines and interview stories.

Proof beats claims

Every CV says "hardworking", "detail-oriented" and "excellent communicator". Recruiters read these words so often that they stop registering. They are claims: statements the employer has to take on trust.

A portfolio offers proof: something the employer can see, open, read or test. A link to a dashboard you built, a marketing campaign you ran for a local business, or a set of financial models with your reasoning explained tells a hiring manager far more than an adjective ever could.

Think about how you choose a fundi to fix your kitchen. You do not just ask whether they are good. You ask to see photos of their past work, or you go by someone who has seen it. Employers think the same way. Hiring is a risk, and evidence reduces risk.

Key idea

Employers hire evidence. A portfolio turns "I can do this" into "Here is where I did it". It matters most precisely when you have no formal job history, because it substitutes for the proof that experience would normally provide.

Choose projects that mirror real job tasks

The most common portfolio mistake is building projects that are impressive to you but irrelevant to the job. A beautiful personal website does little for a credit analyst role. The fix is to work backwards from the jobs you want.

  1. Collect job adverts. Find several real adverts for the role you are targeting, at the level you can realistically reach in the next year.
  2. List the recurring tasks. Read the responsibilities and highlight the tasks that keep appearing: "prepare monthly reports", "manage social media content", "build and maintain APIs", "conduct user research".
  3. Pick two or three core tasks. Choose the ones that appear most often and that you can simulate on your own.
  4. Design a project around each task. Make it as close as possible to what the job would actually ask of you, using realistic data, a realistic audience or a real local problem.
  5. Keep the scope small. A finished, well-explained small project beats an ambitious half-built one every time.

Real problems make the strongest projects. Offer to help a chama organise its contribution records, a church group run its social media for a month, or a family member's shop understand which products sell best. Even unpaid work for a real person counts, and it gives you a genuine result to talk about.

Project ideas by field

Here are examples of portfolio projects that mirror real work. Treat them as starting points and adapt them to the roles and industries you are aiming for.

FieldJob task it mirrorsExample project
SoftwareBuilding and maintaining working applicationsA simple booking app for a local barber or salon, with a clear README, tests and a live demo.
DataCleaning data and turning it into insightAnalyse publicly available data on a topic such as agriculture or transport, then present three clear findings in a short report and a dashboard.
DesignSolving a user problem through designRedesign the sign-up flow of an app you find confusing, showing your user interviews, sketches, wireframes and final screens.
MarketingPlanning and running campaignsRun a one-month social media campaign for a small business, documenting the plan, the content and what happened to engagement.
FinanceAnalysing and modelling financial decisionsBuild a simple budgeting and cash-flow model for a small shop, or a written analysis of a listed company's annual report, with your assumptions stated.
WritingProducing clear content for a defined audienceThree polished pieces in the formats employers need: a blog article, a press release and a short explainer, each aimed at a named audience.
Try this

Open three job adverts for a role you want, copy the responsibilities into one document, and highlight every task that appears more than once. The most-highlighted task is your first portfolio project. You can do this exercise in under an hour.

How to document a project

A project without explanation is only half the proof. Hiring managers want to see how you think, not just what you produced. For every project, write a short case study using four parts.

  1. Problem. What was the situation, and why did it matter? Who was affected? Keep it to two or three sentences.
  2. Approach. What did you do, step by step, and why did you make the choices you made? Mention the tools and methods you used, and any trade-offs you considered.
  3. Result. What changed? Use real numbers where you have them, and be honest where you do not. "The owner now updates stock weekly instead of guessing" is a genuine result.
  4. What you learned. What would you do differently next time? This shows maturity and self-awareness, which employers value highly in early-career hires.

Add visuals where they help: screenshots, charts, before-and-after images or a short screen recording. Keep each case study short enough to read in a few minutes. A busy reader should grasp the problem and result within the first few lines.

Worked example

Imagine Amina, a business graduate aiming for a junior data analyst role. Her aunt runs a small cosmetics shop and keeps sales records in an exercise book. Amina offers to help for free.

  • Problem: The shop often ran out of its best-selling products while slow-moving stock sat on the shelves, tying up cash.
  • Approach: Amina typed three months of handwritten sales records into a spreadsheet, cleaned up inconsistent product names, and grouped sales by product and by week. She built a simple dashboard showing top sellers and slow movers, and agreed a weekly stock check with her aunt.
  • Result: Her aunt now reorders top sellers before they run out and has reduced orders of the slowest items. Amina records what her aunt reports rather than inventing precise figures she cannot verify.
  • What she learned: Data cleaning took far longer than expected, and the dashboard only became useful once it matched how her aunt actually made decisions.

That single project now gives Amina a case study for her portfolio, a CV line and an interview story, as you will see below.

Where to host your portfolio

Your portfolio should be easy to open from a phone, with one link you can put on your CV and in your email signature. Choose the platform your field already uses, so recruiters know where to look.

  • Software: GitHub for your code, with a clear README for each project, plus a live demo link where possible.
  • Data: GitHub or a public notebook platform for your analysis, and a published dashboard or short report for non-technical readers.
  • Design: a design portfolio site such as Behance or Dribbble, or your own simple website, with full case studies rather than only final images.
  • Marketing, finance and writing: a simple personal website, or a well-organised shared folder of PDFs, plus featured posts on LinkedIn.

Whatever you choose, keep it tidy: a short introduction about who you are and what roles you want, three to five strong projects, and your contact details. Quality beats quantity. Remove weak or unfinished work.

Watch out

Protect other people's information. If you used real data from a business or group, get permission and remove names, phone numbers and anything sensitive before publishing. Never publish work you did for an employer or client that belongs to them. And never present group work as solely yours: say clearly what your part was.

Turning projects into CV lines and interview stories

Your portfolio should feed directly into your CV and your interviews. Each project can become a strong CV bullet and a ready-made story.

CV lines

A good CV bullet starts with a strong verb, says what you did, and shows the result. Using Amina's project:

  • Weak: "Helped with data in a shop."
  • Strong: "Digitised three months of handwritten sales records and built a stock dashboard for a small retail shop, helping the owner reorder best-sellers before they ran out."

Put projects under a heading such as "Projects" or "Selected work", with a link to each case study.

Interview stories with the STAR method

Many interviewers ask behavioural questions, such as "Tell me about a time you solved a problem." The STAR method gives your answer a clear shape:

  • Situation: the context. "My aunt's shop kept running out of popular products."
  • Task: your responsibility. "I offered to find out what was selling and when."
  • Action: what you did, in detail. "I digitised the records, cleaned the data and built a weekly dashboard."
  • Result: the outcome, plus what you learned. "She now reorders before running out, and I learned that a tool is only useful if it fits how people make decisions."

Notice how neatly the four-part case study maps onto STAR. If you document projects well, your interview preparation is mostly done. Prepare one STAR story for each project and practise telling it aloud in about two minutes.

You do not need permission to start building proof. You need one small, real problem and the discipline to finish it.

This week, pick your first project from your job-advert exercise, set yourself a deadline of two to four weeks, and write the case study as you go. Finished is the goal.

Key takeaways

  • Employers trust proof over claims, and a portfolio is the proof you can create before your first job.
  • Work backwards from real job adverts and build projects that mirror the tasks that appear most often.
  • Document each project in four parts: problem, approach, result and what you learned.
  • Host your work where your field already looks, keep it tidy, and protect other people's data.
  • Turn every project into a strong CV line and a STAR interview story.
Chapter 3

Validate Before You Build: Testing a Business Idea in Two Weeks

Most new ventures fail for lack of customers, not lack of effort. A step-by-step plan to find out early.

It is easy to fall in love with a business idea. You picture the logo, the Instagram page, the first big order. Then you spend months and your savings building the product, only to discover that not enough people want to pay for it. This is one of the most common and painful ways new ventures fail, and it is largely avoidable. This article shows you how to test an idea with real customers in about two weeks, before you invest heavily in building anything.

Why good ideas fail without customers

Most failed ventures were not built by lazy people. Founders often work extremely hard. The problem is usually that they worked hard on the wrong thing: a product that solved a problem customers did not have, did not care enough about, or would not pay to fix.

The underlying mistake is treating your idea as a fact rather than a guess. When you say "students will love this", you are making a prediction about other people's behaviour. Until real people act on it, by paying, signing up or changing what they do, it remains a guess.

Validation means collecting evidence, as cheaply and quickly as possible, about whether your guesses are true. It does not prove your business will succeed. It reduces the chance that you spend months building something nobody wants.

Key idea

Your business idea is a set of guesses about customers. Validation is the process of testing those guesses with real behaviour before you spend serious time and money building.

Problem, then customer, then solution

Many first-time founders start with the solution: an app, a product, a service. A stronger approach works in the opposite order.

  1. Problem. What painful, frequent or expensive problem exists? Is it a real problem people already try to solve, or one you imagine they should have?
  2. Customer. Who exactly has this problem? "Everyone" is not an answer. "First-year students living in hostels near campus who cook for themselves" is.
  3. Solution. Only once you understand the problem and the customer should you design a solution. Often, what customers need turns out to be simpler than your original idea.

Working in this order protects you from building a clever solution to a problem nobody has.

Writing falsifiable assumptions

An assumption is something that must be true for your business to work. A falsifiable assumption is written so that evidence could prove it wrong. "People want healthy food" cannot be proven wrong, so it is useless for testing. "At least 1 in 5 hostel students we speak to has spent money on a ready-made lunch in the past week" can be checked, and it can fail.

Write three to five assumptions covering the problem, the customer and willingness to pay. Next to each, write what result would count as a pass and what would count as a fail, before you start testing. Deciding the pass mark in advance stops you from reinterpreting weak results as success later.

Customer discovery interviews

Customer discovery means talking directly to potential customers to understand their problems and current behaviour. It is the cheapest form of validation, and the most often done badly.

The biggest trap is asking leading questions: questions that suggest the answer you want. "Would you buy a healthy lunch delivery service?" invites a polite yes. People are kind, and saying yes to a hypothetical costs them nothing.

Instead, ask about past behaviour, which is far more reliable than opinions about the future. Compare:

Avoid (hypothetical, leading)Ask instead (past behaviour)
Would you use an app for this?Tell me about the last time you had this problem. What did you do?
How much would you pay for this?What have you spent on solving this in the past month?
Do you think this is a good idea?What is the hardest part of dealing with this today?
Would you buy it if it were cheaper?Have you looked for other solutions? What happened?

In each interview, talk less and listen more. Do not pitch your idea until the end, if at all. Take notes on exact words people use, because these often become your best marketing language later. Aim for 10 to 15 interviews with people who closely match your target customer.

Try this

End every interview with two questions: "Is there anything I should have asked but did not?" and "Who else do you know who deals with this problem?" The first often reveals the real issue; the second gives you your next interview.

Smoke tests and the minimum viable product

Interviews tell you about problems. To test whether people will actually act, you need a smoke test: a small, low-cost experiment that measures real customer behaviour before the full product exists. Common smoke tests include:

  • A simple landing page. A one-page website describing the offer, with a clear button to sign up, join a waiting list or order. You measure how many visitors take action.
  • Pre-orders. Asking customers to pay, in full or as a small deposit, before the product is delivered. Money is the strongest signal of real demand. Be transparent about when they will receive it, and refund promptly if you do not proceed.
  • A WhatsApp catalogue or status post. List your product or service on WhatsApp Business or share it on your status and in relevant groups, and count genuine enquiries and orders.

The minimum viable product

A minimum viable product, or MVP, is the simplest version of your product that lets you deliver real value to early customers and learn from how they use it. It is not a poor-quality product. It is a deliberately small one. For a food business, the MVP might be cooking twenty lunches in your own kitchen and delivering them on foot, not opening a restaurant.

Build, measure, learn

Eric Ries, in his work on the Lean Startup approach, describes a loop called build–measure–learn. You build the smallest thing that can test an assumption, measure how real customers respond, and learn whether to adjust your idea. Then you go round again. The goal is to make each loop as fast and cheap as possible, so you can learn many times before your money and motivation run out.

Watch out

Compliments, likes and "I would definitely buy that" are not validation. Count only actions that cost the customer something: time, personal details, or money. Also check local rules before selling food, cosmetics or regulated services, even at test scale.

A two-week validation plan

Here is a day-by-day plan you can adapt. It assumes a few hours a day alongside classes or work.

DayTask
1Write down the problem, target customer and proposed solution in one paragraph each.
2List three to five falsifiable assumptions, each with a pass mark and a fail mark.
3Write an interview guide of eight to ten past-behaviour questions. Line up your first interviewees.
4Conduct three to four interviews. Write notes the same day.
5Conduct three to four more interviews.
6Conduct the final interviews to reach 10 to 15 in total.
7Review your notes. Which assumptions held up? Refine your customer and offer.
8Design your smoke test: a landing page, WhatsApp catalogue or pre-order offer, with a clear price.
9Launch the smoke test and share it with your target customers.
10Keep promoting. Record every visit, enquiry, sign-up and payment.
11Follow up with interested people and try to convert enquiries into pre-orders.
12Deliver a small MVP to your first paying customers, if you have any.
13Ask those customers for feedback: what worked, what did not, would they buy again?
14Compare results with your pass marks and decide: persevere, pivot or stop.

Persevere, pivot or stop

At the end of two weeks, you make a decision based on evidence, not hope.

  • Persevere if most of your key assumptions passed and people paid or committed. Keep going, and plan your next build–measure–learn loop at a slightly larger scale.
  • Pivot if you found a real problem but your solution, customer or price was wrong. A pivot is a deliberate change in one part of your plan while keeping what you learned. Perhaps students did not want lunch delivered, but they badly wanted cheap weekly meal-prep ingredients.
  • Stop if the problem turned out not to matter enough to anyone. Stopping after two weeks is not failure. It is a success: you saved months of effort and money, and you learned how to test the next idea.
Worked example

This is a hypothetical example. The idea and all figures are illustrative.

A second-year student in Nairobi wants to sell healthy packed lunches to students in hostels near her campus. Her key assumption: "At least 1 in 5 hostel students regularly buys lunch near campus and is unhappy with the options."

Interviews (days 3 to 7). She speaks to 12 students. Nine of them bought lunch near campus in the past week, and seven complained about price or long queues, not about health. That is a surprise worth noting: her target customers care more about cost and speed than nutrition.

Smoke test (days 8 to 11). She adjusts her offer to "affordable, pre-ordered lunch ready for collection at 1 pm, no queue" and posts it on a simple WhatsApp catalogue shared in three student groups. Over four days, 140 people view the catalogue and 21 send enquiries, which is 21 ÷ 140 = 15% of viewers. Of those 21, 8 pre-order and pay a small deposit.

Decision (day 14). Her pass mark for the smoke test, set on day 2, was 5 paid pre-orders. She received 8, so that assumption passed. She decides to pivot her positioning from "healthy" to "quick and affordable" and persevere with a second, slightly larger test the following fortnight.

Fall in love with the customer's problem, not with your first solution.

Key takeaways

  • Many ventures fail because they build something customers do not want enough to pay for, not because of lack of effort.
  • Work in order: problem, then customer, then solution.
  • Write falsifiable assumptions with pass and fail marks set before you test.
  • In interviews, ask about past behaviour, not hypothetical opinions, and avoid leading questions.
  • Use smoke tests such as landing pages, pre-orders and WhatsApp catalogues, and build a minimum viable product.
  • Run fast build–measure–learn loops, then decide with evidence whether to persevere, pivot or stop.
Chapter 4

Your 30-day launch plan

This plan turns both chapters into action. In the first two weeks, you will build and document one portfolio project. In the second two, you will run a compressed version of the two-week validation from the second chapter. By day 30, you should have one finished piece of proof for employers, and real evidence about whether your idea is worth pursuing. Plan for one to two hours a day alongside classes or work, and record everything in your launch notebook as you go.

Week 1: Choose your proof

This week applies the first half of the portfolio chapter: working backwards from real jobs.

  1. Day 1: Collect job adverts. Find at least three real adverts for the role you named at the start of the book, at a level you could reach within a year. Copy the responsibilities into one document.
  2. Day 2: Highlight recurring tasks. Mark every task that appears more than once. Rank them by how often they appear.
  3. Day 3: Pick one core task. Choose the highest-ranked task you can simulate on your own. Write it at the top of a new page.
  4. Day 4: Find a real problem. Look for a real person or group with that problem: a family member's shop, a chama's records, a church group's social media. If you use their data, ask permission first.
  5. Day 5: Scope it small. Write a one-paragraph project plan that can be finished in about ten days. Cut anything that would take longer.
  6. Days 6 and 7: Start building. Begin the work, and start your case study notes now, recording the problem and each choice you make in your approach.

Week 2: Build, document and present

This week finishes the project and applies the second half of the portfolio chapter: turning work into evidence.

  1. Days 8 to 10: Finish the project. Focus on completing the core task. A finished small project beats an ambitious half-built one.
  2. Day 11: Write the case study. Use the four parts: problem, approach, result and what you learned. Report results honestly, without inventing figures.
  3. Day 12: Add visuals and publish. Add screenshots or charts, remove names, phone numbers and other sensitive details, and host it where your field already looks.
  4. Day 13: Write your CV line. Start with a strong verb, say what you did and show the result. Add it under a "Projects" heading with a link.
  5. Day 14: Prepare your STAR story. Map the case study to Situation, Task, Action and Result. Practise telling it aloud in about two minutes.

Week 3: Test the problem with real people

This week applies the first half of the validation chapter, using the problem you wrote down at the start of the book.

  1. Day 15: Problem, customer, solution. Write one paragraph on each, in that order. Make your customer specific, never "everyone".
  2. Day 16: Write falsifiable assumptions. List three to five assumptions covering the problem, the customer and willingness to pay. Set a pass mark and a fail mark for each, before you test anything.
  3. Day 17: Draft your interview guide. Write eight to ten questions about past behaviour, such as "Tell me about the last time you had this problem". Remove any leading or hypothetical questions.
  4. Days 18 to 20: Interview. Speak to three or four people each day, aiming for 10 to 15 in total. Listen more than you talk, record their exact words, and end with "Who else deals with this problem?"
  5. Day 21: Review your evidence. Compare your notes with your pass marks. Which assumptions held up? Refine your customer and your offer.

Week 4: Test real behaviour and decide

This week applies the second half of the validation chapter: smoke tests, a minimum viable product and an evidence-based decision.

  1. Day 22: Design your smoke test. Choose a simple landing page, a WhatsApp catalogue or a pre-order offer, with a clear price. Check any local rules that apply before selling food, cosmetics or regulated services.
  2. Day 23: Launch. Share it with your target customers through the channels they already use.
  3. Days 24 and 25: Measure. Record every view, enquiry, sign-up and payment. Count only actions that cost the customer something, not likes or compliments.
  4. Day 26: Follow up. Contact interested people and try to turn enquiries into pre-orders. If you take deposits, be clear about delivery dates and refund promptly if you do not proceed.
  5. Day 27: Deliver a small MVP. If anyone has paid, deliver the simplest version that gives them real value, and ask what worked and what did not.
  6. Day 28: Decide. Compare results with your pass marks and choose: persevere, pivot or stop. Write down your reasoning.
  7. Days 29 and 30: Turn it into proof. Write up the validation as a second portfolio case study, whatever the result. A well-reasoned decision to stop is valuable evidence of good judgement.

Your day-30 checklist

  • I have a document of recurring tasks drawn from at least three real job adverts.
  • I have finished one portfolio project that mirrors a real job task.
  • I have a published four-part case study with sensitive details removed.
  • I have a new CV line and a two-minute STAR story I have practised aloud.
  • I have written falsifiable assumptions with pass and fail marks set in advance.
  • I have completed at least 10 customer discovery interviews.
  • I have run one smoke test and recorded the real actions it produced.
  • I have made and written down a persevere, pivot or stop decision based on evidence.
Watch out

The most common way people fall off this plan is by letting the project grow. A ten-day portfolio project becomes a month-long one, or a smoke test is delayed while the logo and website are perfected. Before long, the plan is abandoned with nothing finished. Protect your scope. If something will not fit in the time available, cut it and note it as a future improvement in your case study. Finished and explained always beats bigger and unfinished.

Key takeaways

  • Work backwards from real job adverts and choose a project that mirrors a recurring task.
  • Keep the scope small, finish it, and document it as problem, approach, result and what you learned.
  • Turn every project into a CV line and a STAR story you can tell in two minutes.
  • Test business ideas by writing falsifiable assumptions and asking about past behaviour, not opinions.
  • Count only actions that cost customers something, and decide with evidence whether to persevere, pivot or stop.
  • Whatever the result, a documented test is proof of your judgement and belongs in your portfolio.

Keep learning

Turn what you've read into skills with a structured course or a free tutorial series.

© Kuza Ndoto. Free for personal learning. This eBook is general education, not professional financial, medical or legal advice.