In MitHub's journey (Discover → Learn → Build → Create value → Prove → Earn → Improve), this is the Discover stage. It is short on purpose. The goal is not to find a perfect answer; it is to pick a strong enough direction to start building proof.
Why guessing does not work
Most people try to find their strengths by asking how they feel: what they enjoy, what sounds interesting, what a quiz says. Those signals are useful for choosing where to look, but they have two problems:
- Enjoyment and performance are not the same thing. You can love an activity and be average at it.
- Strengths are often invisible to their owner. Things that come easily feel unremarkable, so people discount them.
Peter Drucker made this point in his Harvard Business Review article Managing Oneself. He argued that most people think they know what they are good at and are usually wrong, and that knowing your strengths matters because people now have far more choice over where they work than in the past. His answer was not reflection. It was a record of results.
Exercise 1: Feedback analysis (Drucker's method)
Drucker described a method he called feedback analysis in Managing Oneself. Whenever you make a key decision or take a key action, write down what you expect will happen. Nine to 12 months later, compare the actual results with your expectations. He wrote that he had practiced it for many years and was surprised every time.
The comparison reveals patterns: where your results consistently match or exceed your expectations, where they fall short, and where you have no ability to perform at all.
How to apply it now:
- Keep a simple log: date, decision or action, what you expect, why.
- Review monthly and do a deeper review at the nine- to 12-month mark, following Drucker's timing.
- For example, if you start a practice automation project and write "I expect to finish in two weeks and cut manual steps in half," you will later learn something concrete about your estimation, your technical speed and your follow-through.
Drucker drew several implications from the analysis. Concentrate on your strengths and put yourself where they can produce results. Work on improving those strengths. And he argued that climbing from incompetence to mediocrity costs much more effort than climbing from first-rate performance to excellence. For someone choosing a career direction in the AI economy, that is a strong argument against spending years patching your weakest area.
Feedback analysis takes months. The next three exercises give you signal this week.
Exercise 2: The results inventory
List outcomes you have produced, not tasks you performed. Look across work, school, side projects, volunteering and family responsibilities.
For each result, write:
- What changed? (A number, a decision, a problem that stopped happening.)
- What did you personally do?
- What made it work? (Your contribution, not the circumstances.)
Aim for 10 to 15 results. Then look for repeats in the third column. If "I noticed the pattern nobody else saw" or "I got people who disagreed to commit" shows up three times, that is a candidate strength backed by evidence.
Common trap: writing "I was responsible for social media." That is a task. "Posts I wrote brought in most of the inquiries for a small business's event" is a result.
Exercise 3: The easy-for-me, hard-for-others test
Answer these questions quickly, without polishing:
- What do people repeatedly ask you to help with?
- What do you do that makes others say "how did you do that so fast?"
- What do you find yourself fixing even when it is not your job?
- What kind of problem do you not mind staying with for hours?
Then ask three to five people who have seen you work, not just friends, one question: "When would you call me instead of someone else?" Write down their exact answers. Look for overlap between their answers and your inventory.
Exercise 4: The two-week strength test
Candidate strengths are hypotheses. Test them with a small, real project that would expose you if you are wrong. This is the same logic MitHub teaches for client work in operate: observe, hypothesis, build, measure, learn, adjust.
For example:
| Candidate strength | Two-week test | What would disprove it |
|---|---|---|
| Spotting patterns in data | Clean and analyze a simulated CRM export, then write three findings | Your findings are obvious or wrong when someone checks |
| Designing processes | Map how a local business handles a new customer inquiry and redesign it | The owner cannot follow your redesign |
| Explaining technical things | Write a one-page explanation of an automation for a non-technical owner | They cannot repeat back what it does |
| Persuading and closing | Get three people to agree to a meeting about a specific problem | Nobody responds or agrees |
Log your expectations before starting. That turns each test into a small feedback analysis.
Connect strengths to value: the MitHub Strength-to-Value Map
A strength with no market is a hobby. A strength tied to an outcome a company pays for is a career. A simple lens helps: companies pay for revenue gained, time saved, cost avoided or risk reduced. Trace the money backwards, as the faculty teaches in follow the money, and ask where your strength touches it.
Chapter 5 of the faculty, operate, describes three roles in GTM work. They are a practical way to map strengths to value:
| If your evidence shows strength in... | Natural role | Outcome a business pays for |
|---|---|---|
| Patterns, numbers, asking "why did this change?" | Analyst | Knowing where revenue leaks and which fix matters most |
| Building, connecting systems, debugging | Engineer | Processes that run without manual work, faster lead response, clean data |
| Explaining, listening, managing expectations | Client-facing | Clients who understand the value, stay and expand |
Most people have a primary and a secondary role. That combination is a starting point for a skill stack; see the skills that make you more valuable.
Then place yourself on MitHub's capability ladder: Doer → Director → Designer → Owner. Your strength tells you where to climb; the ladder tells you how high your current evidence goes. A strong analyst who can only produce reports by hand is a doer. The same analyst who designs a reporting system and owns the decisions it drives is much more valuable.
Why this matters more in the AI economy
As AI takes over more repetitive work, the premise of the new game, generic effort becomes less distinctive. What remains distinctive is the combination of strengths you bring to directing, designing and owning systems.
Employers are also naming self-knowledge directly. In the World Economic Forum's Future of Jobs Report 2025, motivation and self-awareness rank fifth among the core skills employers say workers need today, behind analytical thinking; resilience, flexibility and agility; leadership and social influence; and creative thinking. Knowing your strengths is not a soft extra. It shapes where you invest limited learning time.
Put it together: a two-week plan
- Day 1: Start your feedback analysis log. It will pay off in months.
- Days 2–3: Write your results inventory. 10 to 15 results.
- Days 4–5: Run the easy-for-me test and ask three to five people.
- Day 6: Choose two candidate strengths that appear in both.
- Days 7–13: Run a one-week version of the strength test on the strongest candidate.
- Day 14: Map it to a role and an outcome using the Strength-to-Value Map.
The output is not a label. It is a direction plus the first piece of evidence. From there, move into learn, build, prove, earn. If you want a broader sense of direction that includes what you care about, ikigai for career direction is a useful companion.
Mistakes to avoid
- Treating a quiz result as a conclusion. Use it as a hypothesis to test.
- Confusing access with ability. Having done something because you were the only one available is not the same as being good at it. Check the result.
- Waiting for certainty. Strengths get confirmed by doing work, not before it.
- Ignoring the market. A strength you cannot connect to revenue, time, cost or risk will be hard to get paid for.
Find the evidence, test the hypothesis, connect it to value, then build proof. That is how knowing yourself becomes becoming more valuable.