
One App for
Learning & Reflection
Look back at what you enjoyed doing and why.
See a possible direction take shape in your LifeTask map.
Choose a skill to learn through audio lessons and practice.
A memory
“I used to take things apart to see how they worked.”
Then I’d sketch ways to put them back together.
“I used to take things apart to see how they worked.”
Product design
Your curiosity about how things work could lead you toward product design.
Product design
Your curiosity about how things work could lead you toward product design.
Pillars
Seeing how parts fit
Frictions
Refining for too long
Your traits
How you learn
A skill to develop


From Product Idea to Testable Prototype
2 hr 44 min audio · 13 lessons · 7 practices
Learn to turn a product idea into a focused prototype, test it through realistic tasks, interpret the evidence carefully, and choose a useful next iteration.
Curriculum
Choose the uncertainty your first prototype must answer12 min
›Practice: Write your first prototype decision brief15 min
›Turn an uncertainty into a realistic task and observable result12 min
›Match prototype fidelity to the evidence you need13 min
›Design a test that can support a clear decision12 min
›Practice: Build a focused prototype test plan25 min
›Generate alternatives before investing in one solution11 min
›Shape the product around its sequence of use13 min
›Practice: Sketch three use driven forms25 min
›Use ergonomic reasoning for fit, reach, and handling13 min
›Build a physical mockup that exposes the right questions14 min
›Practice: Make a question driven physical mockup40 min
›Prototype an interface as states and transitions14 min
›Run a test without coaching the participant15 min
›Practice: Conduct and record a short prototype test35 min
›Interpret results within the limits of the test12 min
›Choose an iteration that teaches you something new13 min
›Practice: Plan one evidence based iteration25 min
›Assemble a complete prototype and testing cycle10 min
›Practice: Complete a fresh end to end prototype challenge60 min
›Choose the uncertainty your first prototype must answer
Imagine a countertop jar opener for people who find gripping and twisting lids painful. A jar slides into a V-shaped cradle, an upper arm engages the lid, and the user moves a long lever. Even in that short description, the idea depends on many things being true. The opener must address a real difficulty, accept the jars people use, hold them securely, require manageable effort, fit on a counter, and survive repeated loading. Your first prototype should not attempt to settle all of that. Its job is to investigate one uncertainty that matters to a decision you are ready to make.
An uncertainty is an important fact or relationship that you do not yet know. It is more specific than a feature category. Usefulness, usability, size, operation, appeal, materials, and durability are useful areas to inspect, but none is a test question by itself. “We are uncertain about usability” could mean that people may not know where to place the jar, may orient it incorrectly, or may be unable to move the lever. A useful uncertainty identifies what may fail and under what conditions. For example, “Can people secure jars of the intended sizes without gripping the jar body tightly?”
That question exposes an assumption already embedded in the design. The V-shaped cradle assumes that its angle, surface, and method of tightening can restrain different jar widths. The lever mechanism then depends on that restraint. If the jar rotates when force reaches the lid, improving the lever handle will not solve the more basic problem. This is why an early prototype question should come from the structure of the idea, not merely from the feature that is easiest or most enjoyable to build.
A consequential uncertainty is one whose answer could alter a substantial commitment. It might change whether you continue with the concept, which users you design for, or which physical arrangement you develop. Suppose the cradle cannot hold common jars unless the user squeezes them firmly with the other hand. That result would challenge the intended benefit and could lead you to compare a clamp, a self-centering ring, or a different product direction. By contrast, uncertainty about the exact contour of the lever handle may not yet redirect the concept. Handle shape matters, but refining it before the jar can be restrained would improve a dependent detail while leaving the central arrangement unresolved.
Consequences are not measured only by how serious a question sounds. They also depend on how many later choices rely on the answer. Product ideas contain dependencies, meaning that one design choice creates conditions for several others. In the opener, jar restraint affects the lever position, the base dimensions, the direction of force, and the need for a second hand. If you develop all four around an ineffective cradle, much of that work may need to be discarded. The best first question is usually the one whose answer could redirect the product and whose dependencies would otherwise carry a weak assumption into later work.
Some dependencies concern the product’s reason for existing rather than its mechanism. If you have little evidence that painful lid opening is frequent or important for the intended users, usefulness may sit upstream of the cradle geometry. A mechanically successful opener would not establish that people need another countertop object or would choose this approach over existing tools. In that situation, observing recent experiences with jars or comparing current coping methods may deserve priority. There is no rule that usefulness must always be tested first. The priority depends on what is already known and what the project currently assumes without adequate support.
Dependency also affects the order in which closely related questions can be answered. Imagine testing whether the opener’s lever requires comfortable effort. If the rough cradle allows every jar to slip, the test will reveal little about the intended lever action. Slipping prevents the later interaction from occurring under credible conditions. Restraint is therefore a gate for the force question. But dependencies are not always a simple chain. Counter fit and jar restraint might be tested independently because neither result requires the other. Look for genuine gates, where failure in one relationship makes evidence about another relationship difficult to interpret.
Importance alone is not enough. The uncertainty must also be testable in the present stage of the project. Present testability means that you can create a representation and a situation capable of producing relevant evidence now. You do not need certainty, a finished product, or a large study. You do need some observable difference between a direction that appears worth continuing and one that should be reconsidered. A full-size adjustable mockup could reveal whether the cradle accommodates the intended jar range and whether jars remain restrained during a careful trial. It could not establish whether the opener remains reliable after years of repeated loading.
When an important question is not presently testable, narrow it or choose another kind of investigation. “Will the mechanism be durable in daily use?” includes material fatigue, wear, contamination, manufacturing variation, and thousands of cycles. A few movements of a cardboard joint cannot answer it. An early, narrower question might be whether the proposed joint has enough clearance to complete its motion without colliding with the jar. Long-term durability may later require engineering calculations, material specimens, repeated-cycle testing, or production-like components. Calling the cardboard movement a durability test would not make its evidence relevant.
The reverse problem is choosing a question simply because it is convenient to test. You might be able to compare two handle profiles in an afternoon. That comparison could produce clear preferences, yet still have little effect on whether the current arrangement deserves development. Easy questions often feel productive because they produce immediate answers. A useful priority decision asks what uncertainty threatens the intended benefit, what later work depends on it, and whether relevant evidence is possible now. These considerations work together. No single one should be used as an automatic ranking formula.
Now connect the chosen uncertainty to a design decision. For the jar opener, the uncertainty could be whether the V-shaped cradle can secure the intended range of jars without requiring strong grip from the user. The decision could be whether to retain that cradle arrangement or develop a different restraint mechanism. This does not yet specify the complete test task or a numerical standard. Those come later. It does establish why you are collecting evidence and which commitment is open to change.
Ask what evidence could realistically move that decision in either direction. If several people can place representative jars, engage the restraint, and begin the opening action without gripping the jar body, continued development of the cradle becomes more reasonable. If they repeatedly need a second hand to prevent rotation, that evidence supports reconsidering the restraint. A mixed result might reveal that the arrangement works only for part of the intended jar range, leading to a narrower product scope or an adjustable alternative. In each case, the evidence changes a real choice rather than merely generating comments.
This is the weakness of a vague aim such as, “Let’s see whether people like the opener.” People may like the purpose, admire the lever, dislike the appearance, or imagine a price that was never mentioned. Their reactions can be sincere while referring to different parts of the idea. General approval also gives the designer no clear response. If praise and criticism would both lead to building the same design, the exercise has not informed a decision. Preference is useful when preference itself controls a meaningful choice, but it should not stand in for evidence about performance, fit, or need.
The evidence you can obtain is limited by prototype fidelity. Fidelity means how closely a prototype represents particular properties of the intended product. It is not one overall level from crude to realistic. A model can have accurate dimensions but unrealistic weight, or a working joint with unfinished surfaces. For the opener, a full-size wooden base with adjustable blocks might represent jar spacing and stability well while saying little about final appearance or manufacturing cost. A foam handle might support an early grasp comparison but cannot establish whether molded plastic will remain comfortable during repeated high-force use.
Match any conclusion to the property the prototype actually represents. If the base is much lighter than intended, tipping may be an artifact of the model rather than evidence against the final arrangement. If hidden tape makes the cradle unusually sticky, successful restraint may also be misleading. Too little fidelity can remove the behavior you need to study. Excessive fidelity creates a different problem: time and attention go into finished surfaces, realistic colors, or concealed construction even when those properties add no evidence for the current decision. A polished model can also invite judgments about purchase appeal and make a tentative arrangement appear more settled than it is.
The first prototype therefore needs enough credibility in the selected relationship, not realism in every property. For the cradle question, that may require representative jar widths, accurate contact geometry, plausible movement, and enough base stability for the opening action. It does not yet require a production material, a final visual finish, or evidence about years of wear. Those unresolved matters should remain visible in your notes so that a successful early trial is not mistaken for validation of the whole product.
A sound first prototype begins with a bounded claim about what you need to learn. Identify the uncertainty that could change an important commitment, examine which later choices depend on it, and decide whether a prototype can represent the relevant conditions now. Then name the design decision that different evidence could alter. That gives the prototype a precise responsibility while preserving the many questions it is not capable of answering.
A journal that helps you identify your Life’s Task and keeps you on track
- Prompts to help you start reflecting
- Get a clear LifeTask hypothesis
- Weekly updates and quarterly reviews to keep you on track
Your past
One chapter at a time ↓
- 1
Earliest Memories
- 2
Early School Years
- 3
Teenage Years
- 4
After School Choices
- 5
Early Experience and Skills
- 6
Work or Projects
Your LifeTask map
Product design
You enjoy taking things apart, sketching alternatives and trying them out. Product design could give you more of that in your work.
Pillars
Spotting practical problems
Thinking in three dimensions
Learning through prototypes
Finding simpler solutions
Frictions
Refining for too long
Testing ideas too late
Taking criticism personally
Create your next course in one click
- LifeTask researches the topic and creates the curriculum
- Approve the curriculum and get audio lectures
- Complete practice sessions and track your progress
What would you like to learn?
You’ll be able to review the curriculum and change it if you want before we start building your course.
Suggestions for you
Explain your
ideas clearly
Researching clear explanations

Clear Communication at Work
2 hr 35 min audio · 15 lessons · 7 practices
Learn to shape, support, deliver, and adapt clear explanations for conversations, meetings, and short presentations.
Curriculum
Choose your main point12 min
›Practice: Find the real point8 min
›Start with what the listener knows10 min
›Decide what to include10 min
›Practice: Shape the explanation before speaking10 min
›Put your ideas in a clear order11 min
›Help the listener follow your reasoning9 min
›Practice: Create a listener-friendly route12 min
›Support your point with evidence11 min
›Choose useful examples and analogies10 min
›Explain numbers and comparisons10 min
›Practice: Support a point without overloading it15 min
›Explain an idea in conversation10 min
›Make your point in a meeting11 min
›Prepare a short presentation10 min
›Practice: Adapt one idea to three speaking settings18 min
›Use pace, pauses, and emphasis10 min
›Answer questions clearly10 min
›Practice: Practice the question turn15 min
›Find and fix a misunderstanding10 min
›Prepare, explain, and adapt11 min
›Practice: Final practice: explain, respond, and adapt25 min
›Choose your main point
A topic tells you what you are speaking about. A point tells the listener what to take from it. That difference is the first practical step toward explaining anything clearly.
Suppose someone says, “I need to explain our new appointment system.” That identifies a topic: the new appointment system. It does not yet tell us what the explanation is meant to accomplish. Perhaps employees need to understand why the system is changing. Perhaps customers need to know how to book an appointment. Perhaps a manager must decide whether to approve the change. Those explanations share a topic, but they need different main points.
For employees, the point might be, “The new system should reduce scheduling conflicts because it prevents two people from booking the same time.” For customers, it might be, “From Monday, you can book, change, or cancel an appointment through the online form.” For the manager, it might be, “We should adopt this system because it addresses our main scheduling problem without increasing administrative work.”
Notice what has changed. Each sentence gives the topic a direction. It selects what matters for a particular listener and indicates what should be different after the explanation. One listener should understand a reason. Another should know what to do. Another should accept or assess a recommendation.
Before you decide what details to include, choose that intended change. Complete this sentence: “When I finish, I want this listener to understand that...” Then finish it with a full claim.
The words “understand that” matter. If you say, “I want the listener to understand the appointment system,” you still have only a subject. What about the system should become clear? Perhaps that it prevents duplicate bookings, that it changes the customer’s next step, or that it will not replace telephone support. A complete sentence forces you to say what the listener should carry away.
The sentence frame uses “understand,” but the intended change can involve understanding, belief, or action. These are related, but they are not identical. You may want someone to understand how a process works. You may want someone to believe that a proposal is worthwhile. Or you may want someone to do something next.
If the desired change is understanding, your point states the idea or relationship that should become clear. “I want this listener to understand that the delay is caused by a shortage of components, not by slower assembly.” That tells you the explanation must clarify a cause and perhaps correct a likely misunderstanding.
If the desired change is belief, your point states the conclusion you want the listener to accept or seriously consider. “I want this listener to believe that delaying the launch by one week is less risky than releasing the product with a known payment error.” This does not mean manipulating the listener. A responsible explanation gives reasons and preserves relevant uncertainty. The intended belief tells you which conclusion those reasons must support.
If the desired change is action, your point identifies what the listener should do and, usually, why. “I want this listener to understand that they need to submit the form by Thursday so their request can be considered this month.” The deadline is not just a fact. It has a consequence, and that consequence gives the action its significance.
Often an explanation involves all three kinds of change. A colleague may need to understand a problem, believe that one response is sensible, and then approve a decision. Even so, one of those changes usually governs the explanation. Ask which result is needed now. If a manager is already convinced that a project matters but does not know what decision is required, more persuasion may be unnecessary. The useful point is probably the requested action. If a customer knows what button to press but doubts that the process is secure, further instructions will not address the real issue. The useful point concerns trust and the reason for it.
This is why starting with everything you know often produces a weak explanation. Your knowledge of a subject may include its history, terminology, exceptions, benefits, risks, and technical details. But the listener does not need your knowledge reproduced in the order you acquired it. They need a path toward a particular understanding. Once you name the intended change, you can judge each detail by asking whether it helps produce that change.
Consider an everyday personal example. You want to explain to a friend why you cannot attend a weekend event. The topic is your schedule. A broad explanation might include your work deadlines, travel time, family plans, and recent lack of sleep. But perhaps the real point is simply, “I cannot attend on Saturday because I have already committed to caring for a relative, but I am available on Sunday.” That point gives the friend the fact that matters and the practical alternative. A complete history of your week would add information without improving understanding.
A useful main point therefore has to survive three common failures. The first is merely announcing the subject. “I’m going to explain the budget” tells the listener where you are going, but not what matters about the budget. “The proposed budget covers our essential costs, but it leaves no allowance for equipment failure” makes a point. Now the listener knows the central judgment that the explanation will support.
The second failure is making the point too broad. “Good communication is important in every organization” is a claim, but it gives an explanation very little direction. It could lead to a discussion of leadership, customer service, conflict, documentation, meetings, or dozens of other matters. A more useful point might be, “Confirming responsibilities at the end of a meeting reduces missed handoffs because each task has a named owner.” The revised point identifies a practice, an outcome, and the relationship between them.
Broad points often contain words such as “important,” “better,” “effective,” or “problematic” without saying in what way. These words are not always wrong, but they invite a useful question. Important for what? Better by which relevant standard? Effective at producing which result? Problematic because of what consequence? Answering that question usually turns a general opinion into an explainable claim.
The third failure is packing several competing messages into one sentence. Imagine this intended point: “I want the listener to understand that the training is useful, registration closes Friday, the sessions are too long, the software has changed, and managers should encourage attendance.” This is not one point. It is a small collection of points with no clear hierarchy.
To repair it, decide what the listener most needs to retain. If you are speaking to employees, the main point might be, “Register by Friday if you need to use the updated software next month.” The changed software explains the relevance of the training, and Friday gives the required action. The length of the sessions might still matter, but it belongs later if it affects planning. If you are speaking to managers, the main point might instead be, “Managers should protect time for the training because employees will need the updated software next month.” The same situation now produces a different central sentence.
A point can contain more than one clause. The goal is not to produce the shortest possible sentence. The goal is to produce one coherent message. “We should delay the move until Tuesday because the building’s network will not be active on Monday” contains a recommendation and its central reason, but both clauses serve one conclusion. By contrast, “We should delay the move, redesign the office, review the supplier contract, and survey employees” asks the listener to retain several decisions at once.
When several messages genuinely matter, place them under one governing point. Suppose a project update includes higher costs, a late supplier, and a revised completion date. You could treat these as three separate facts. But if the listener must decide whether to continue, the governing point may be, “The project can still meet its essential goal, but only if we approve the revised cost and completion date.” The supplier delay then becomes support for that point rather than a rival for attention.
This does not mean that you must know every detail before choosing a point. Sometimes speaking or preparing reveals that your first point was wrong. Perhaps you begin with “The delivery will be late because the supplier made an error,” then discover that your own order was submitted after the deadline. Accuracy requires changing the point. The sentence is a working commitment, not a device for forcing evidence to fit a preferred conclusion.
It is also useful to distinguish your point from your private motive. You might want a customer to stop complaining, a colleague to approve your idea, or a family member to agree with you. Those desires do not automatically produce a fair explanatory point. Ask what the listener has good reason to understand, believe, or do. “I want them to agree with me” is not enough. Agree about what, and on what grounds? A better statement would be, “I want the customer to understand that the fee resulted from using the service after the free period ended, and that they can prevent another charge by cancelling today.” That gives the explanation an accurate and useful purpose while leaving room for the customer to question the policy.
Then test whether the point fits the listener. A technically accurate sentence can still be the wrong point. An engineer may need to understand why a component fails under high temperature. A customer using the product may need to know only that it should not be left in a hot vehicle. Accuracy is required in both cases, but usefulness determines the level and direction of the explanation.
Finally, imagine that the listener remembers only one sentence tomorrow. Would this be the right sentence? It should preserve the understanding or next step you wanted to make clear.
If it would not be the right sentence, revise it. Replace the topic with a claim. Narrow a broad judgment by naming the relevant result. Separate competing messages and choose the one that governs the others. Make the listener and the needed next step more specific. You are ready to build an explanation when you can say, in one clear sentence, what this particular listener should understand, believe, or do after hearing you.
Make the recommendation
Three worn laptops stopped employees’ work this week. Your manager accepts that replacement is necessary and must decide today whether to buy them this month or next quarter.
Which main point should govern your explanation?
The manager already accepts the need for replacement. This point addresses the timing decision and gives a relevant reason for buying this month.
There is more content than I could ever consume. LifeTask helps me identify what is relevant to the work I want to do and turns it into a learning path I can follow.
LifeTask feels like an agentic education experience. It learns from my reflections, connects them to my goals, and creates the next lesson around what I need to develop.
After finishing my MBA, I had more options but less certainty about which direction fit me. LifeTask helped me connect my strengths, values, and experience into a career path I could act on.
I knew what I was studying, but not where it could take me. LifeTask helped me understand the kind of work that fits me and gave me clarity about the internships and skills I should pursue next.
The experts agree
Meaningful work starts with attention to what is uniquely yours: your interests, your energy, and the problems you are willing to commit to.
“At your birth a seed is planted. That seed is your uniqueness. It wants to grow, transform itself, and flower to its full potential. It has a natural, assertive energy to it. Your Life’s Task is to bring that seed to flower, to express your uniqueness through your work.”
“Everyone is capable of both deep interest and boredom. Move toward what interests you and away from what bores you. I think the most important decision you can possibly make in a career, is to make sure you have immense passion for what you’re doing.”
“Life is suffering. So figure out something worth suffering for. You’re going to suffer either way. And that’s another thing I think people don’t realize, is there isn’t really a path that is easy that I’ve ever found.”
For people trying to figure out
what kind of work and life fits them best.
Whether you are choosing a direction, rethinking a career, or trying to reconnect with what makes your work feel meaningful, LifeTask gives you a structured way to investigate instead of guessing.
What gives me energy?
What am I uniquely good at?
What should I build next?
Most people don’t live life according to
their own principles.
They follow expectations, chase status, or simply take the next available path.
Then one day they wake up feeling exhausted and disconnected, wondering how they ended up building a career that feels wrong. Some people call it burnout, others career confusion.
We believe that you simply lost sight of your Life’s Task.
Our mission is to help you (re)discover it.


Speak with confidence

Venture Capital

Educational Marketing

Home Gardening Essentials

The art of negotiation

The Roman Empire

Write a story worth sharing

The psychology of your Life’s Task

