A problem-solving record connects one observable project obstacle with an action tried, the resources used, and an honest account of what changed. Keep the result separate from your interpretation, then choose a follow-up that addresses the uncertainty still remaining.
The challenge-to-action worksheet below is designed for a student project or early entrepreneurial activity. It helps you document a response to an existing problem without turning an incomplete attempt into a claimed success story.
Describe the obstacle in observable terms
Write what is happening, where it occurs, and which part of the project it affects. Record what you know directly and what someone else reported. Keep your explanation of the cause separate from those observations.
An obstacle statement should make investigation possible. “People don’t care” assigns a motive you may not know. A record that a required response hasn’t arrived tells you what to check and which person or process may have the missing information.
Identify the point in the project where progress stops. A missing answer, an unavailable material, and a disagreement about requirements are different obstacles. Describe the one you can observe rather than grouping every difficulty into a claim that the project is failing. Keep the statement narrow enough that a practical action could produce information about it.
Record the effect separately from the presumed cause. The effect may be that a task cannot begin or an output cannot be checked. The cause may still be unknown. If you start with an unsupported explanation, you may choose an action that tests your assumption rather than investigating the actual obstacle. Leave room for a different explanation to emerge.
List the limits you need to respect
Record the time, materials, approvals, and people available for the task. Identify commitments you can’t change yourself. A proposed solution isn’t usable if it depends on permission or resources you haven’t obtained.
Ask what would make the attempt unsuitable to continue. That may be a deadline, a missing approval, or the risk of disrupting someone else’s work. Keep the action small enough to investigate the immediate problem without creating a larger obligation.
Distinguish a firm constraint from a preference. A required approval is different from a preferred way of organizing the work. Ask the person responsible when you are unsure which applies. The record should make clear what can be adjusted by the team and what requires someone else’s decision, so an attempt doesn’t create an obligation you cannot authorize.
Set a boundary for the attempt before starting it. Identify what you are willing and able to do, what resources you can actually use, and when you will pause to review. Keep unconfirmed support outside the available-resource list. A plan that depends on a hoped-for answer should show that dependency rather than describing the action as ready to begin.
Choose an action that can answer a question
State what you plan to try and what you expect it to clarify. If you change several things at once, be cautious about attributing the result to one change. Record enough detail that you can explain what was actually attempted.
The University of Edinburgh’s reflection guidance connects describing an experience with examining its meaning and planning future action. Apply that separation here: the attempt produces an observation, and your review determines what the observation can reasonably tell you.
Write the question first, then select an action that could help answer it. If the question concerns a missing requirement, the useful action may be to ask the responsible office for clarification. If it concerns an unclear work product, you may need an appropriate review of that product. The action should be connected to the uncertainty rather than chosen merely because it is easy to perform.
Decide what evidence would count as an answer. Keep a request, a response, and a confirmed result as separate stages. If an action produces no answer, record that fact and consider whether the route, timing, or question needs changing. Don’t claim that the action resolved the obstacle simply because the team completed the activity it planned.
Identify resources before asking for them
List the information, materials, or advice you need and the appropriate source. A campus enterprise center, project adviser, library, or relevant staff member may be a place to ask, depending on what your institution provides.
For current information about a separate education opportunity, consult the official grant homepage. Don’t treat a possible grant as a resource already available to your project. This worksheet is not an application formula, eligibility test, or award selection strategy.
Make each resource request specific. State the information, material, or guidance needed and explain its connection to the obstacle. Ask the appropriate person whether they can provide it or identify another route. A broad request for support may be difficult to act on when the missing resource has not been defined.
Record what is offered and under which conditions. Access to advice is different from permission to use a space, and a referral is different from approval. Put the actual response into the worksheet and keep any remaining requirement visible. This allows the team to plan from available resources without overstating what another person or office has committed to provide.
Use a challenge-to-action worksheet
Keep each record focused on one obstacle. Add a date whenever you update the observation or decide on another action.
| Record field | Your entry |
|---|---|
| Obstacle and supporting observation | ______ |
| Effect on the project | ______ |
| Constraints and permissions | ______ |
| Question the attempt should answer | ______ |
| Action tried and date | ______ |
| Resources used | ______ |
| What changed and what did not | ______ |
| Remaining uncertainty and follow-up action | ______ |
Keep sensitive information out of any version shared with a group. You can describe a missing resource or an unresolved process without exposing someone else’s personal records.
Add entries in time order. Keep the original obstacle statement, then record the attempt and the observation it produced. If your understanding of the obstacle changes, add a dated revision explaining why. That history helps a teammate see how the project reached its current position without relying on a retold account that makes the sequence appear simpler than it was.
Separate “what changed” from “what we think it means.” A response received, a missing field identified, or a resource made available is an observation. A conclusion that the entire project is now viable requires more evidence. Keep the interpretation proportionate to the result, and use the remaining uncertainty to decide whether another action is worthwhile.
Walk through a fictional campus-project illustration
Fictional illustration: a student group cannot confirm a room for a product demonstration. The record identifies the missing room approval, the event date, and the staff contact listed in the campus booking process. The group sends the required information and asks whether anything is missing.
The response identifies an incomplete booking field. The group corrects it and records that the request is now under review. It does not write “venue secured” until confirmation arrives. This is an invented teaching illustration, not a real case study or a claim of business success.
In this fictional example, the first useful result is clarification of the missing booking information. That is narrower than securing a venue, but it still changes what the group knows. The worksheet should record the clarification, the correction submitted, and the fact that approval remains pending. The follow-up is then tied to the campus office’s actual response process.
If the request is later declined, the group would record that decision and ask what options, if any, are available within the project’s limits. It would not rewrite the original attempt as a successful booking. The illustration shows how a record can preserve useful learning even when an action does not produce the hoped-for outcome. It is not an account of a real project or a claim that a particular response will be available.
What should a problem-solving record contain?
- An observable obstacle and its constraints.
- The action tried and resources used.
- What changed and what remains uncertain.
- A dated follow-up action or decision to stop.
Let the record determine the follow-up
Review what the attempt established before choosing another action. Continue when there is a useful question to answer, seek help when a decision exceeds your authority, and stop when the activity no longer serves the project. The record should show honest learning from a specific obstacle, not manufacture a success story.
References
University of Edinburgh Reflection Toolkit: What? So what? Now what?
