Recognize what is open to interpretation
A request such as “improve the onboarding process” or “take a look at our inventory” names an area of work, but it does not define the result. You may need to decide what problem matters most, how much time to spend and what a useful first deliverable looks like. That can feel like a missing instruction. It may also be an invitation to propose a direction.
Before starting, separate what you know from what you are assuming. Note the requested outcome, the deadline, who will use the work and any limits on time or resources. Then list the unanswered questions. Does “improve onboarding” mean rewriting instructions, finding recurring problems or creating a checklist? Naming those possibilities makes the assignment easier to discuss and prevents you from committing to one interpretation without noticing.
Clarify the outcome, not every step
You do not need a detailed set of instructions to make progress. You do need enough agreement to avoid working toward the wrong goal. Ask the person who assigned the work what a useful result would help them decide or do. Questions such as “Who is the audience?”, “Which problem should I address first?” and “What would be useful by Friday?” often reveal more than asking for a complete procedure.
Offer a proposed plan when you ask. For example: “I can review the current instructions, identify the three most confusing steps and suggest revisions. Is that the right starting point?” A concrete proposal gives a colleague something to confirm or redirect. It also shows initiative without pretending that you have information you do not have.
If you cannot get an immediate answer, choose a small first step that is easy to adjust. Reviewing existing materials or sketching two possible approaches is usually less costly to revise than building a full solution around an untested assumption.
Rank work using impact, urgency and dependencies
Once the goal is clearer, list the tasks that could move it forward. Rank them by three practical questions: Which task would make the biggest difference to the intended outcome? Which has a real time constraint? Which tasks must happen before others can begin? These questions help distinguish a useful priority from an activity that simply feels productive.
For an onboarding project, talking with the people who use the current instructions might come before redesigning their layout. A polished document will not solve much if it addresses the wrong difficulties. On the other hand, if new staff arrive next week, a short correction to a misleading step may be more useful now than a complete rewrite later.
Be explicit about tradeoffs. If you have several assignments, ask which should take precedence when their deadlines compete. You might say, “I can finish the checklist this afternoon or spend that time resolving the inventory issue. Which would you prefer first?” This makes the decision visible rather than silently treating every request as equally urgent.
Work in short cycles and share what you learn
Open-ended work becomes easier to manage when you set a near-term checkpoint. Decide what you can produce in a few hours or days: a brief outline, a sample, a list of problems or a draft recommendation. A checkpoint lets others respond while a change of direction is still relatively easy.
Keep updates concise and specific. State what you completed, what you learned, what you plan to do next and where you need a decision. For example: “I reviewed the guide and found two steps that people interpret differently. I’ll draft clearer wording for both. Should I also include a short checklist?” This is more useful than a general update that says only that the project is underway.
When priorities change, revisit the plan rather than treating the original one as fixed. New information may reveal a more pressing problem or a dependency you missed. Adjusting the order of work is not the same as abandoning it; it is a way to keep the effort connected to its purpose.
Build a repeatable approach
Experience with structured work can help you notice dependencies, communicate progress and follow through. In a less structured assignment, those same habits remain useful, but you may have to define the first milestone yourself. A repeatable sequence can help: describe the desired outcome, identify what is unknown, propose a small first step, rank the remaining tasks and agree on a checkpoint.
After the assignment, take a moment to note which questions helped and which assumptions needed correction. You do not need to eliminate uncertainty before beginning. The aim is to make uncertainty visible, take a sensible step and give others a chance to steer the work before too much time is spent in the wrong direction.
