Student guide · A Steven Bryan Project
Turn learning into evidence.
SPARK is a career-development habit you can use in any major. Choose one useful task, practice a skill, keep your work, learn from someone and explain the result.
Skills · Portfolio · AI usage · Relationships · Knowledge in Action.
What you will leave with
- A specific skill to practice and a small project you can finish or test.
- An artifact with a clear record of your own contribution.
- An honest explanation of AI assistance and how you checked it.
- Feedback you acted on and a respectful follow-up.
- A result, limitation and next step you can explain in a portfolio or interview.
SPARK does not assign a grade, guarantee employment or certify your skills. Strong evidence lets another person inspect what you did. You can use it independently or alongside a class.
Your first 15 minutes
- Pick one task. Choose something small: reconcile six records, explain a concept, improve a checklist or compare two options.
- Name the audience and success check. Who needs this? What would make the result useful and checkable?
- Choose one skill. “Check totals and explain differences” is more useful than “get better at Excel.”
- Plan the artifact and feedback. Decide what you will keep and who could help you improve it.
- Start an entry. Open the workspace, record the plan, then do the work. Return to record what actually happened.
Expect the project itself to take longer than the reflection. The weekly entry can take about 10 minutes after you have done the work. Save unfinished entries honestly; “pending” is better than an invented result.
The five habits
| Habit | Do this | Keep this evidence |
|---|---|---|
| S · Skills | Choose one technical, business or human skill. Practice it on a real or clearly labeled simulated task. | What you practiced, a check and what still needs work. |
| P · Portfolio | Keep an artifact someone else can inspect. Explain the problem, your method and your contribution. | A file or approved link, version and short explanation. The app stores notes, not attached files. |
| A · AI usage | Use AI thoughtfully when appropriate. Keep only claims you can support; disclose accepted and rejected assistance. | Tool/date, important prompt/output, your decisions and independent checks. No AI use is also acceptable. |
| R · Relationships | Ask a peer, tutor, mentor or professional a focused question. Listen, contribute and follow up. | The feedback actually received and what you did with it. Record pending replies as pending. |
| K · Knowledge in Action | Apply the concept to a decision, change or test. Explain what happened and what remains uncertain. | An observed result or clearly labeled estimate/proposal, its limits and your next action. |
Use the five habits together; you do not need five unrelated projects. One small project can provide evidence for every part.
A flexible four-week starting path
| Week | Focus | Finish with |
|---|---|---|
| 1 · Choose and begin | Set a baseline, pick one skill and begin a small artifact. | A project question, success check, first draft and honest notes about the gaps. |
| 2 · Build and check | Practice the skill, improve the artifact and independently verify important claims. | A checked version and a clear account of AI help or no AI use. |
| 3 · Learn from people | Ask for focused feedback. Test a suggestion and contribute something useful in return. | A revised artifact, feedback record and follow-up. A pending response is not completed feedback. |
| 4 · Apply and explain | Use the artifact, test the result and prepare a concise portfolio explanation. | A problem → action → evidence → result → limitation story, plus the next growth target. |
Record all five SPARK areas each week when you can; they will deepen as your project develops. Repeat the cycle with a new task or continue the same project. A missing area is a next action, not failure.
Worked example: a club equipment handoff
Illustrative simulation. The student, peer feedback and AI interaction below are fictional. Use the structure; do not present these actions or results as your own.
Task: prepare six equipment records for a club event so a teammate can see where each item belongs. The supplied fictional file has 24 units and three blank station assignments.
Download the six-row practice CSV.
Fictional event brief: cones, balls, flags and bibs belong at Field; the pump and first-aid kits belong at Equipment. Keep the original file and create a revised copy. Do not invent a purchase price or a time-saving result.
- S · Skill
- Organize equipment records and independently reconcile the quantity total. Manually add 8 + 4 + 2 + 6 + 1 + 3 = 24.
- P · Portfolio
- Keep the original and revised CSV, a handoff checklist and a note explaining the three station assignments filled using the event brief. The student filled the gaps and checked the counts.
- A · AI usage
- In this fictional example, AI suggested a checklist and incorrectly described 25 units. The student rejected that number, retained a clearer checklist heading and checked the total independently. Keep actual exchanges for your own work.
- R · Relationships
- A fictional teammate asked for separate check-out and check-in columns. The student tried that suggestion and showed the revision. In your work, ask a real peer or tutor; never invent a conversation.
- K · Application
- The revised six-row file has 24 units and zero blank stations. This verifies completion of the simulated record-cleaning task. It does not prove that a real event ran faster or that equipment losses fell. Next: ask a teammate to test the handoff.
A portfolio explanation
“I revised a six-record simulated equipment inventory using a supplied event brief. I reconciled 24 units, filled three station assignments and documented the original and revised versions. I rejected an incorrect AI count and added clearer handoff fields after feedback. The next check is a teammate test; real event outcomes have not been measured.”
This describes the example’s scope and limits. Your own portfolio explanation must describe your actual contribution and evidence.
Use AI without handing over responsibility
- Use a school-approved tool and follow the assignment’s rules. Do not paste confidential records, grades, credentials or private contact details into a prompt.
- Ask for questions, alternatives or a critique before asking for a finished answer.
- Check factual claims against the original source. Check calculations manually or with an independent method.
- Do not let AI invent experience, references, relationships, certifications or results.
- Record your decisions. “AI helped” is less useful than “AI suggested three headings; I kept one, revised two and verified the totals.”
A safe coaching prompt
“I am practicing [skill] through [task]. My audience is [audience], and success means [check]. Ask me three questions that could improve my plan. Do not invent results or experience. Label suggestions that need evidence.”
A verification prompt
“Review this explanation for claims that require a source, calculation or test. Separate what the supplied evidence supports from what is an inference. Do not replace missing evidence with a confident answer.”
These prompts support your review; AI’s agreement is not independent verification.
Make one useful connection
Start with someone accessible: a classmate, tutor, instructor or colleague. Professional networking can begin with a focused learning conversation rather than a request for a job.
- Ask a small, respectful question about the work. Ask permission before sending an artifact.
- Listen and identify one suggestion you can test.
- Follow up with what changed and thank them for their time.
- Contribute something useful when appropriate. Respect a declined request or no reply.
Example request to adapt: “I’m practicing [skill] through a small [project]. Would you be willing to look at [one part] and tell me what is unclear? It should take about five minutes. No problem if your schedule is full.”
The app does not send messages or store anyone’s contact information. Do not record private details or imply someone endorsed your work without permission.
Prepare one strong evidence card
Include the problem and audience, artifact, your contribution, checked result, AI/collaborator credit, limitation and next step. Keep the actual file outside the app, with a sensible version name.
- Specific: a reader can see what you did.
- Inspectable: the reader can follow the artifact or source.
- Honest: simulations, estimates and pending outcomes are labeled.
- Credited: your contribution and assistance are clear.
- Shareable: permission and privacy have been checked.
You do not need to publish every artifact publicly. Some evidence belongs in a private instructor review or interview discussion. A local filename is a reminder, not a public link.
For instructors and mentors
Use a short weekly check-in or a four-week mini-project across majors. Model a small evidence card before asking students to create one. Let students use synthetic data and peer feedback when workplace data or professional access is unavailable.
Give feedback on observable work: Does the artifact support the claimed skill? Can the student explain a check? Are limits and assistance labeled? What changed after feedback? Do not judge a student’s ability by the number of contacts, the prestige of a mentor or AI access.
This product supplies a learning routine and self-review, not an institutional assessment policy. Set any required length, grading, accommodation or submission rules separately. Collect only needed evidence through approved school systems.
Keep and protect your work
Does my instructor see my entries? No. This version has no account, classroom dashboard or submission service. You decide what to export and share.
Will my notes follow me to another computer? No. Download a JSON backup and restore it in the other browser. Offline and hosted copies may use separate browser storage.
What if browser saving fails? Keep the tab open and download a backup. Private browsing, storage limits and browser settings can affect saving.
Can I use it without AI? Yes. Record “No AI used.” AI access is not a requirement for participation.
What if I have no feedback yet? Label the request or reply pending. Keep the card as work in progress and record the actual response later.
What does the sharing checklist mean? It records your review. The app does not authenticate your evidence or certify professional readiness.
Printable weekly worksheet
My weekly SPARK
Project: ______________________________ Date: ______________
My task, audience and success check
S · What skill did I practice? What still needs work?
P · What artifact can I show? What part did I do?
A · How did AI help, and how did I check it? Or: no AI used.
R · Who did I learn from? What feedback and follow-up?
K · How did I apply it? What result, limit and next action?
☐ Checked claims and limits ☐ Credited contributions ☐ Checked permission/privacy
An unfinished or pending result is acceptable when labeled honestly. Keep the actual artifact and sources.
Framework origin
Built from Steven Bryan’s recovered SPARK Master Blueprint v0.2, dated 5 September 2026. The original expands Skills as Strategic Capabilities, Portfolio as Professional Portfolio, AI as AI Fluency, Relationships as Relationships & Reputation, and K as Knowledge in Action. This product keeps the simple student labels requested by Steven Bryan.
Download the original career SPARK blueprint.
This career-development product is separate from the SPARK + TRACE course capability-profile framework: Self, Position, Augment, Relationships and Knowledge to Proof.