Back to portfolio
Governance, Legal & PeopleSimulated project

Web3 Educator / Curriculum Builder portfolio brief

A simulated governance, legal & people exercise for Web3 Educator / Curriculum Builder. Treat it as realistic practice, not real client or protocol work.

Objective

Choose the developer or user track

Expected deliverables

Curriculum mapLessonWorkshopExerciseAssessment rubricFacilitator guideLearner feedback report

Recommended workflow

  1. Choose the developer or user track
  2. Define one real learner task and prerequisites
  3. Build, test, and revise a short lesson with evidence of learning
  4. Review the result against the rubric, then package it as a case study.

Constraints and safety

  • Use only public sources or clearly simulated data.
  • Never include seed phrases, private keys, or wallet secrets.
  • Redact private user, company, security, legal, or compensation information.
  • State every assumption you make.

Tools in practice

Docs or LMS
Draft, review, and maintain curriculum map and lesson, with owners, source links, and change history.
GitHub and sandboxes for developer track
Inspect technical source material and maintain versioned work connected to curriculum map and lesson.
presentation tools
Turn the analysis behind curriculum map and lesson into a reviewable decision narrative for internal or external stakeholders.
forms and assessment tools
Create diagnostic questions, exercises, assessments, and learner feedback forms tied to specific learning objectives.
analytics
Measure the role-specific signals behind curriculum map and lesson and document attribution, time window, and known gaps.
community platforms
Run cohort discussion, answer learner questions, collect misconceptions, and route technical corrections to subject-matter reviewers.

What a strong submission shows

  • A curriculum map
  • One complete lesson and exercise
  • An assessment rubric
  • A revision based on learner errors

Weak submission patterns

  • Slide decks with no learning objective
  • Content consumption counted as mastery
  • Developer tutorials that have not been run

Review rubric

  • Accuracy of claims and sources
  • Relevance to the target role
  • Decision quality and trade-offs
  • Completeness of the deliverable
  • Clarity of communication
  • Honest limitations and next steps

Present it as a case study

  • Explain the problem, sources, decisions, ownership, constraints, output, review, and what you would change.
  • Show the final artifact before the process notes.
  • State what you owned and what belonged to other people.
  • Label the work as simulated, and keep any real contribution clearly separate.

Interview questions this project helps you answer

  1. How do the two education tracks differ in technical hiring requirements?

  2. How do you assess whether someone can actually perform the task?

  3. What do you remove when a lesson is accurate but overloaded?

Turn this into an application