Career Artifact Build

Today you build the portfolio itself. One request before you start: don't title it "Future Esports CEO" or anything resembling a senior executive bio. You're a high school student building evidence of what you're learning to do. That's the honest version, and it's also the stronger one — a portfolio that overclaims invites the exact scrutiny it can't survive.

Your portfolio identity

Open with four short lines: your name or student identifier, your current interests, the skills you're building, and the career area you're exploring. Not a lifelong-expert bio.

Example About section: "I'm a high school student exploring esports event operations, media, and technology. Through this course I've worked on team systems, communication protocols, digital audits, career research, and project testing. I'm currently interested in learning more about event production and technical operations." That's believable, specific, and enough.

Portfolio architecture

Version 1 needs five sections: About, Skill 1 plus evidence, Skill 2 plus evidence, Skill 3 plus evidence, and Next Step. Keep it to that — a five-section portfolio that's actually finished is worth more than a ten-section portfolio that's half-built.

Build each project card

Every artifact you selected in Lesson 2 gets: project name, the problem it addressed, your contribution, the artifact itself, the skill it demonstrates, the evidence or result, and one thing you'd improve.

Worked example, using the Team Routine Prototype:

Problem. Practice preparation depended too heavily on one team leader.

My contribution. I mapped role ownership and developed the backup step.

Artifact. A process diagram plus a Version 1 and Version 2 comparison.

Skill. Process design and problem solving.

Evidence. During the first simulation, removing the team captain stopped the routine entirely. Version 2 added a backup owner, and the second simulation completed without that failure.

What I would improve. Test the routine with participants who had never seen the process before.

Notice this card doesn't claim a perfect project — it shows real thinking, including what didn't work the first time. That's stronger evidence than a claim of flawless execution.

Screenshots need a purpose

Don't include a large screenshot just because screenshots look official. Ask what the viewer should notice, and annotate if it helps — an arrow pointing at the change you made, a circled conflict point from an earlier version, a caption naming where the change came from. The visual should carry part of the story, not just decorate the page.

Use before-and-after where it exists

If a project literally contains iteration — the Week 5 Practice Improvement Experiment, the Week 6 Team Routine Prototype, or the Week 10 Positive Interaction Prototype — show Version 1 next to Version 2 with a short line about what changed and why. That's some of the strongest evidence available in this course, so don't leave it on the table.

Make your three cards cover different ground

Avoid telling the same story three times. For an event-operations direction, for example: the Team Role Blueprint could demonstrate organization, the Communication Protocol could demonstrate operational communication, and the Digital Citizenship Audit could demonstrate risk and audience analysis. Together, three different dimensions of the same career direction are more convincing than three variations on one skill.

Closing a gap with a small new artifact

If your existing work doesn't demonstrate an important skill for your direction, you're allowed to build one small new piece of evidence — not a full production, just enough to close the gap.

Media. A simple broadcast graphic or a 30-second edited clip.

Event operations. A one-page tournament operations checklist.

IT. A troubleshooting flowchart for a fictional esports station.

Analytics. One small match-analysis visualization from instructor-provided fictional data.

Social media. A three-post event communication plan using fictional information.

Web. A wireframe for a team event page.

Coaching. A replay-review template.

Don't build fake experience

"Managed tournament operations for 500 participants" is a strong claim — and it's a lie if you didn't do it. "Designed a tournament-operations workflow for a classroom simulation" is accurate and still useful. Your portfolio should document what you've actually done, not what would sound impressive.

The same standard applies to language. If a sentence reads like it was pulled from generic corporate writing — "leveraged synergistic cross-functional collaboration to optimize outcomes" — replace it with a plain description of the project. Clear verbs and a real explanation carry more weight than borrowed vocabulary.

Build it

You have roughly fifteen to twenty minutes. Produce: About and direction; Artifact 1; Artifact 2; Artifact 3; Next Step.

The Next Step section

This may be the most important page. Answer: what evidence is currently missing? If you say you're interested in video but have no video sample, that gap is your next project.

Build a short evidence-gap table: for each skill your target career needs, note whether you have strong, partial, or no evidence, and name one possible next project if there's a gap. That turns career planning into something actionable instead of a wish list.

Peer review

Give a partner 90 seconds with your portfolio and no explanation from you. Afterward, they answer: what career direction do you think this student is exploring; what three skills do you think they're demonstrating; which artifact is strongest; and which claim has the weakest evidence. If they can't answer, the portfolio needs revision before it's done.

Accessibility and privacy check

Confirm readable text, strong contrast, clear headings, image descriptions where the platform supports them, diagrams that make sense without relying on color alone, and descriptive links. Then confirm: no private student data, no personal contact details, group work credited, external media credited, no private screenshots, no unauthorized personal information. Your class portfolio does not need to be public to meet these standards — it needs to meet them regardless of where it lives.

Final defense

Your instructor selects one of your three artifacts. In 60 seconds, answer: what skill does this demonstrate, what did you personally contribute, what evidence supports the claim, and what would you improve next. If you can answer all four without hesitating, the artifact belongs in your portfolio.

Final requirements

Your Career Evidence Portfolio needs: a short About section, a stated career direction, three work samples, an individual contribution statement for each, a skill claim for each, evidence or result for each, one improvement note per artifact, one evidence-gap analysis, one next-project or skill target, credit for any group or external work, and privacy-safe content throughout.

Before you leave

Look at your finished portfolio and mentally delete all the skill labels. Could someone still infer some of your skills from the work itself, without the labels telling them? If yes, the evidence is doing its job.

Source note

This project directly supports Middle Township's career-readiness focus on professional value, marketability, transferable skills, reflection, and career planning. The district also recognizes portfolios and student-created digital work as valid evidence of learning.

CareerOneStop's portfolio guidance emphasizes work samples, project context, individual contribution, quality, and organization.

The Career Evidence Portfolio architecture, evidence-gap analysis, mini-artifact options, and portfolio defense are original Robotnix Academy components.