Shape the Future of STEAM Education as a Pedagogical Lead

Partner with developers to create impactful educational simulators and earn revenue share in the STEAM StartUp program
Get Started
THE PEDAGOGICAL LEAD ROLE

You Are the Simulator Creator!

As a Pedagogical Lead, you are the principal responsible for your simulator project. You:

  • Lead the project from concept to completion
  • Own the educational vision and learning outcomes
  • Ensure quality standards across all simulator elements
  • Guarantee curriculum alignment with educational programs
  • Serve as subject matter expert for your simulator
  • Make final decisions on pedagogical approach and content
  • Coordinate with Technical Developers to implement your vision

This is not a support role, it's a leadership position.

YOUR RESPONSIBILITIES AS PROJECT LEADER

Educational Design & Quality Assurance:

  • Define learning objectives aligned with educational standards
  • Ensure simulator accuracy and educational validity
  • Create comprehensive lesson plans (EASE template)
  • Develop assessment strategies and rubrics
  • Verify curriculum alignment across grade levels
  • Test simulator effectiveness with target audiences

Project Management:

  • Lead the development process with your Technical Developer
  • Set priorities and approve features
  • Provide expert feedback throughout development
  • Ensure deadlines and quality standards are met
  • Approve final simulator before launch

Subject Matter Expertise:

  • Serve as the expert reference for your simulator topic
  • Validate scientific/technical accuracy
  • Answer educator questions post-launch
  • Update content as educational standards evolve
REQUIREMENTS & QUALIFICATIONS

Essential Qualifications:

  • Subject matter expertise in the simulator topic area
  • Educational credentials (teaching degree, relevant certifications)
  • Proven teaching experience in STEAM education
  • Curriculum development experience
  • Quality assurance mindset - attention to detail
  • Leadership skills - ability to guide technical team
  • Understanding of pedagogical best practices

Preferred:

  • EASE certified e-trainer status (earn 2 credits instead of 1)
  • Experience with educational technology
  • Published educational materials
  • Curriculum alignment experience (national/international standards)
YOUR AUTHORITY & OWNERSHIP

As Pedagogical Lead, You Have:

  • Final approval on all educational content
  • Veto power on features that compromise educational value
  • Decision authority on simulator scope and features
  • Quality control responsibility
  • Credit as project leader on the simulator
  • Recognition as the expert behind the simulator

Your name and credentials appear on:

  • Simulator credits page
  • Lesson plan documentation
  • Platform directory of leads
  • Marketing materials (with permission)
REVENUE & RECOGNITION

How You Earn:

  • 1 credit per simulator (standard Pedagogical Lead)
  • 2 credits per simulator (EASE certified e-trainer)
  • Credits = ownership stake in STEAM StartUp
  • Quarterly revenue distribution (every 3 months)
  • You earn more because you lead more

Why 1-2 Credits vs Developer's 3?

The Technical Developer receives 3 credits for implementation work, but you:

  • Own the intellectual property of the educational design
  • Maintain long-term responsibility for quality
  • Serve as ongoing expert resource
  • Can lead multiple projects simultaneously

Become EASE Certified E-Trainer:
[Click here to find the certification programme] - Double your credits per simulator

THE LEADERSHIP PROCESS

Your Journey as Pedagogical Lead:

Phase 1: Concept & Approval

  • Submit your simulator proposal
  • Define learning objectives and scope
  • Get approval from STEAM StartUp review board

Phase 2: Team Formation

  • Be matched with a Technical Developer
  • Establish roles and communication protocols
  • Set project timeline and milestones

Phase 3: Educational Design

  • Create detailed lesson plan (EASE template)
  • Define all educational content and materials
  • Specify learning activities and assessments
  • Align with curriculum standards

Phase 4: Development Leadership

  • Brief Technical Developer on requirements
  • Review and approve prototypes
  • Provide expert feedback iteratively
  • Ensure educational effectiveness

Phase 5: Quality Assurance

  • Test simulator with target users
  • Verify all learning objectives are met
  • Check curriculum alignment
  • Approve final version

Phase 6: Launch & Maintenance

  • Final sign-off for platform launch
  • Monitor educator feedback
  • Update content as needed
  • Maintain expert support
QUALITY STANDARDS YOU ENSURE

Educational Alignment:

  • Maps to recognized educational standards (NGSS, Common Core, etc.)
  • Appropriate for target age/grade level
  • Achieves stated learning objectives

Scientific/Technical Accuracy:

  • Content is factually correct
  • Simulations reflect real-world principles
  • No misleading or oversimplified information

Pedagogical Effectiveness:

  • Engages students in active learning
  • Supports multiple learning styles
  • Includes formative assessment opportunities
  • Provides scaffolding for different skill levels

Usability:

  • Clear instructions for educators
  • Intuitive for students
  • Accessible to diverse learners
  • Technical stability

FAQ's

Do I need technical skills?

No. Your Technical Developer handles coding. You need educational expertise and the ability to communicate your vision clearly.

Can I lead multiple simulators?

Yes! Many successful leads manage 2-5 simulators in their expertise area.

What if the Technical Developer doesn't meet quality standards?

You have authority to request changes. If unresolved, STEAM StartUp mediates or reassigns developers.

Am I responsible for bugs?

No. Technical issues are the developer's responsibility. You're responsible for educational quality and content accuracy.

Can I update my simulator after launch?

Yes. As the leader, you can request updates to maintain relevance and quality.