Skip to main content

Independent candidate proof of work

From HBS research to experiential AI learning

One challenge in the HBS AI Institute Instructional Designer role stood out to me: translating emerging faculty research into learning experiences executives can understand, practice, and apply. Rather than only describe how I would approach that work, I tested the process myself.

In a few focused hours, I researched the public role specification, reviewed HBS AI studies, selected a peer-reviewed research foundation, and built a complete 60-minute executive workshop — along with the participant, facilitator, measurement, accessibility, and AI-enabled production systems required to support it.

Independent candidate prototype created using publicly available HBS research. Not an official Harvard Business School product.

The translation path
  1. Research paper

    Peer-reviewed field experiment

  2. Executive decision

    Where should AI act, and who verifies?

  3. Learning experience

    60-minute experiential working session

  4. Workplace experiment

    Seven days, one task, one decision rule

Project at a glance

Current role specification analyzed
1Current role specification analyzed
HBS / Harvard AI research candidates reviewed
9HBS / Harvard AI research candidates reviewed
Peer-reviewed study selected
1Peer-reviewed study selected
Minute experiential workshop
60Minute experiential workshop
Slide facilitation deck
24Slide facilitation deck
Page participant workbook
14Page participant workbook
Page facilitator guide and SOP
19Page facilitator guide and SOP
Page complete portfolio
39Page complete portfolio
Slide interview presentation
7Slide interview presentation
Assessment levels: before, during, after, later
4Assessment levels: before, during, after, later
Day transfer measures
7/30/90Day transfer measures
Reusable safeguarded production prompts
15Reusable safeguarded production prompts

The goal was not to create the greatest possible quantity of material. The goal was to demonstrate an end-to-end research-to-learning production system.

01 — The challenge

Can complex AI research become something an executive can understand, practice, and apply?

The job description calls for more than conventional content production. It requires an instructional designer who can connect faculty, subject-matter experts, facilitators, and program teams; translate academic research into participant-centered experiences; produce assets across formats; support delivery; measure performance and impact; and build AI-enabled production systems that improve over time.

I treated those responsibilities as the project specification.

Role responsibilities mapped to what they mean in practice and to evidence in this project
Role responsibilityWhat it means in practiceEvidence in this project
Research translationPreserve findings and limitations while converting them into executive decisionsFaculty research brief, claim ledger, framework rationale, workshop
Experiential learningMake participants perform a meaningful taskFrontier Fit Map based on a real organizational workflow
End-to-end asset productionProduce a connected learning system rather than isolated slidesDeck, workbook, facilitator guide, takeaway card, assessment, digital specification
Facilitation readinessMake another facilitator capable of delivering the experienceMinute-by-minute guide, speaker notes, backup demo, misconceptions, contingencies
MeasurementDemonstrate learning and transfer rather than satisfaction aloneBaseline, rubric, post-performance task, 7/30/90-day follow-up
AI-enabled productionUse AI to accelerate repeatable work while retaining human accountabilityProduction workflow, approval gates, SOP, prompt library, versioning
Continuous improvementCombine learner data, facilitator observations, and faculty reviewFeedback instrument, analysis process, revision example
View the complete HBS Role → Evidence Map

Opens the portfolio PDF. The map appears near the beginning and again at the end of the document.

02 — Research

Research first. Curriculum second.

I reviewed public HBS and Harvard AI research for three qualities: evidentiary strength, executive relevance, and the ability to support an experiential activity rather than a passive lecture.

Nine candidates reviewed. Scoring scale: 1 = weak fit, 10 = exceptional fit. Scores are prototype judgments, not Harvard ratings. Expand a candidate for researchers, finding, relevance, exercise concept, and the selection judgment.

Selected research

A useful tension: AI improved performance — until task fit changed.

Navigating the Jagged Technological Frontier: a preregistered, randomized field experiment with 758 working consultants on tasks designed to resemble their work, published in Organization Science in 2026.

Inside the tested frontier

  • +12.2%more subtasks completed
  • 25.1%faster
  • ≈32%higher quality, following the HBS AI Institute's public interpretation

Outside the tested frontier — correctness on the task

  • 84.5%no-AI group correct
  • 70.6%GPT-4 group correct
  • 60%GPT-4 plus overview group correct

The same broad technology category did not create the same result across similar-looking knowledge-work tasks. The practical leadership problem is therefore not simply whether to adopt AI. It is how to test task fit and assign authority.

What this research does not prove

This study does not prove that every model, worker, industry, or workflow will produce the same results. The experiment used a specific 2023 version of GPT-4, a consultant sample, and designed work tasks. The location of the capability boundary changes.

The selected research is public HBS-affiliated research. The learning framework and executive application are my instructional translations and require faculty validation.

Sources

All figures above are drawn from the cited paper and the HBS AI Institute summary. Any executive implication beyond those figures is a prototype implication and requires faculty validation.

03 — The translation

The executive problem is not “Should we use AI?”

It is: Where should AI act, where should a human verify, and what evidence justifies that decision?

  1. Research finding

    “AI capability is uneven across tasks.”

  2. Executive problem

    “Similar-looking workflows may require different operating modes.”

  3. Learning capability

    “A leader can test one task and assign AI an evidence-based role.”

  4. Participant output

    “A seven-day experiment with a baseline, quality metric, accountable human, escalation condition, and stop rule.”

04 — Backward design

I designed backward from what the participant should be able to do.

By the end of the experience, a participant can decompose a real workflow, form a hypothesis about AI fit, design a representative test, assign an appropriate human–AI operating mode, and define a measurable seven-day experiment.

Learning objectives aligned to required knowledge, activity, and evidence of learning
Participants can…Required knowledgeLearning activityEvidence of learning
Decompose one business workflow into observable tasks and decision pointsWorkflow versus task; inputs, outputs, handoffs, exceptionsWorkflow strip and task decompositionAt least 4 distinct tasks with owners, inputs, outputs, and failure consequences
Form an evidence-based hypothesis about where AI may help, harm, or remain uncertainJagged frontier; coherence versus correctness; moving boundaryFrontier prediction on each taskRationale cites task characteristics rather than personal enthusiasm
Design a representative comparison test for one taskBaseline, representative case, acceptance criteria, failure modeTest-plan canvas and demo auditTest includes baseline, 3–5 cases, quality metric, and stop rule
Assign an appropriate AI–human operating mode and guardrailAI-led, human–AI, human-led; verification and escalationMode decision matrix and peer challengeRole assignment includes accountable human, verification source, and escalation condition
Commit to a seven-day experiment that can produce a go, revise, or stop decisionTransfer, iteration, monitoringAction-plan cardNamed owner, first case, metric, review date, and decision rule

The deck is not the product. Improved decision capability is the product.

05 — The framework

The Frontier Fit Loop

A repeatable, five-step decision procedure a leader can run without a facilitator present. Select a step to see the guiding question, the participant action, the evidence produced, and the most common mistake.

Monitor returns to Decompose: the frontier moves when models, data, staff, or regulation change, so a passing test is a dated result rather than a permanent classification.

Step 1 of 5 · Decompose

Break the workflow into observable tasks. Name the inputs, outputs, decisions, owners, handoffs, and consequences.

Guiding question
What action begins and ends?
Participant action
Write 4–7 observable tasks for one real workflow.
Evidence produced
A task strip with owners, inputs, outputs, and failure consequences.
Most common mistake
Describing a job or department instead of a testable task.

Operating modes: assign authority, not just tasks

The decision that matters most is not which tool to buy. It is who holds authority, on what evidence, and under what condition the work stops.

  • AI-led

    Strong repeated evidence; errors are detectable, reversible, and low-consequence.

  • Human–AI

    Mixed evidence or meaningful context; independent human verification required.

  • Human-led

    Weak evidence or high-stakes, novel, regulated, difficult-to-verify, or irreversible consequences.

Every mode requires a named accountable human, an independent verification source, an escalation condition, and a stop rule.

Candidate-created instructional translation. Requires HBS/faculty validation.

06 — The workshop

Sixty minutes, designed as a decision rehearsal

Learn → see → do → reflect → apply → commit

Over half the session is participant work. The design sequence deliberately places prediction before evidence, and evidence before practice on the participant's own workflow.

  1. 0–5min

    Learn / predict

    Provocation

    “A faster answer can still be the wrong answer.” Individual vote and paired rationale make prior belief visible.

    Participant actionVote on whether a polished, faster AI recommendation should be deployed.

    Workshop deck

  2. 5–12min

    Learn

    Research insight

    Study design, inside-frontier gains, outside-frontier losses, and stated limitations.

    Participant actionIdentify what makes a polished but incorrect output dangerous in their domain.

    Workshop deckParticipant research brief

  3. 12–20min

    See / reflect

    Mental model

    The jagged frontier and the Frontier Fit Loop, applied to a short familiar example.

    Participant actionClassify one task as promising, uncertain, or restricted and document why.

    Workshop deckWorkbook

  4. 20–30min

    See / do

    Live demonstration

    Northstar versus Harbor. Structured metrics favor Northstar; a qualitative constraint reveals that the critical distribution agreement cannot transfer. The AI produces a polished Northstar recommendation from the visible metrics.

    Participant actionChoose independently, inspect the AI output, rate confidence, uncover the missing constraint, and diagnose which Frontier Fit step failed.

    Workshop deckFacilitator guidePrepared demo inputsBackup AI output

  5. 30–45min

    Do

    Participant exercise

    Participants apply the Frontier Fit Map to a real workflow: outcome, baseline, observable tasks, inputs, repeated decisions, human judgment, failure consequences, AI-fit hypothesis, representative cases, quality rubric, stop rule, operating mode, accountable human, escalation condition, success metric, and seven-day action.

    Participant actionBuild a Frontier Fit Map and test plan for one consequential, repeatable task.

    Participant workbookWorkshop deckFacilitator guide

  6. 45–53min

    Reflect

    Peer challenge and debrief

    Participants exchange maps and challenge assumptions: Where could a polished error survive? Is the test representative? Is the metric meaningful? Is the action reversible? Where should the human checkpoint move?

    Participant actionRevise the decision after peer challenge.

    Workbook peer-review pageWorkshop deck

  7. 53–58min

    Apply

    Workplace application

    Participants convert the map into a small, reversible, decision-producing experiment.

    Participant actionSet owner, first case, metric, review date, and decision rule.

    WorkbookExecutive card

  8. 58–60min

    Commit

    Commitment

    “In the next seven days, I will test ______ before allowing AI to ______.”

    Participant actionState the commitment and complete the post-assessment.

    Executive cardWorkbookPost-performance assessment

Selected slides and why they exist

Thirteen of the twenty-four slides, with the instructional reason each one is in the deck.

Slide 2 · Opening provocation

A faster answer can still be the wrong answer

  • more
  • faster
  • less correct
  • Deploy? yes / no / not enough evidence

Text reconstruction of the workshop deck · prototype

Instructional purpose

Surfaces prior belief before evidence arrives, so participants can later observe their own judgment changing.

The live demonstration: a polished, confident error

Stage 1

The setup

A fictional company must choose a launch market. Structured metrics favour Northstar over Harbor. Participants decide independently, on the record, before any AI output appears.

Stage 2

The AI output

Given only the visible metrics, the AI produces a fluent, well-structured, confident recommendation for Northstar. Participants rate their confidence in it.

Stage 3

The reveal

A qualitative constraint shows the critical distribution agreement cannot transfer. The revised decision is a bounded feasibility test — and participants diagnose which Frontier Fit step failed.

The demonstration is not designed to embarrass the technology. It is designed so that overreliance is experienced rather than described — the AI is not wrong because it is weak, but because the evidence it was given was incomplete.

The company, market data, and constraint are fictional teaching content created for this prototype. A prepared backup output is included in case live AI access fails.

07 — Participant experience

The exercise is the product

Participants do not practise on a case study. They map a real workflow they own, design a test for it, assign authority, and leave with a seven-day experiment.

The completed example is a fictional escalation-triage workflow, filled in to the standard the rubric rewards.

  1. Field 01

    Current workflow

    Name one consequential, repeatable workflow you own.

    Facilitator watches for
    Watch for job titles instead of workflows. Redirect to a process with a start and an end.
    Scored as
    Task decomposition — 3 points requires 4–7 observable tasks with inputs, outputs, decisions, owners.
  2. Field 02

    Desired outcome

    What would improve, and for whom?

    Facilitator watches for
    Push past “use AI more.” Ask what the business would notice.
    Scored as
    Feeds the metrics criterion; a vague outcome produces a vanity metric later.
  3. Field 03

    Observable tasks

    List 4–7 tasks with inputs, outputs, and owners.

    Facilitator watches for
    Scan for granularity. Tasks must be small enough to test individually.
    Scored as
    Task decomposition, 0–3.
  4. Field 04

    Human judgment

    Where does judgment actually happen?

    Facilitator watches for
    This column usually predicts where the human checkpoint belongs.
    Scored as
    Supports the authority-and-guardrail criterion.
  5. Field 05

    Failure consequences

    What happens if the task is done badly?

    Facilitator watches for
    Irreversibility is the strongest signal against AI-led authority.
    Scored as
    Authority and guardrail, 0–3.
  6. Field 06

    AI capability hypothesis

    Promising, uncertain, or restricted — and why?

    Facilitator watches for
    Require a task characteristic in the rationale, not enthusiasm.
    Scored as
    Frontier hypothesis, 0–3.
  7. Field 07

    Representative test cases

    Choose 3–5 cases including at least one edge case.

    Facilitator watches for
    Ask what a case that would embarrass the pilot looks like.
    Scored as
    Test design, 0–3 — demo only scores 0.
  8. Field 08

    Quality criteria

    How will output be scored, and by whom?

    Facilitator watches for
    Same rubric for baseline and AI-assisted output, or the comparison is void.
    Scored as
    Test design, 0–3.
  9. Field 09

    Stop rule

    What would make you stop the pilot immediately?

    Facilitator watches for
    The most commonly missed field. A success metric is not a stop rule — say so explicitly.
    Scored as
    Authority and guardrail, 0–3.
  10. Field 10

    Operating mode

    AI-led, human–AI, or human-led?

    Facilitator watches for
    Require the accountable human by role, not “the team.”
    Scored as
    Authority and guardrail, 0–3.
  11. Field 11

    Success metric and decision rule

    What result would justify a wider pilot?

    Facilitator watches for
    Check that the rule can produce a stop, not only a go.
    Scored as
    Metrics and action, 0–3.
  12. Field 12

    Next action

    Seven-day action, owner, review date, go/revise/stop rule.

    Facilitator watches for
    Small, reversible, and decision-producing. Nothing larger.
    Scored as
    Metrics and action, 0–3. Maximum total 15.

Fictional teaching example. Assessment thresholds are prototype judgments requiring faculty validation.

Before, during, and after the session

The experience is a supported system rather than a single event: the facilitator, the participant, and the learning team each hold a defined set of assets at every stage.

Before the session

Facilitator prepares

  • Faculty research brief
  • Claim ledger
  • Facilitator guide
  • Technical readiness checklist
  • Prepared live demonstration
  • Baseline assessment

Participant receives

  • Workshop objective
  • Short research summary
  • Baseline capability questions
  • Workflow-selection prompt

During the session

Facilitator prepares

  • 24-slide workshop deck
  • Speaker notes
  • SAY / ASK / DO / WATCH FOR / DEBRIEF guidance
  • Timing cues
  • Prepared and backup demonstration outputs

Participant uses

  • Workbook
  • Frontier Fit Map
  • Test-design worksheet
  • Peer-challenge prompts
  • Seven-day experiment card

After the session

Learning team uses

  • Post-performance rubric
  • Participant feedback instrument
  • Facilitator observations
  • 7-, 30-, and 90-day transfer measures
  • AI-assisted feedback analysis
  • Human-reviewed revision recommendations
  • Version-control process

Participant uses

  • Executive reference card
  • Completed experiment plan
  • Follow-up prompts
  • The Frontier Fit Loop on new workflows

08 — Measurement

Satisfaction is not evidence of learning

Performance is measured before, during, immediately after, and later — against decision quality rather than activity.

Before

  • Baseline concept comprehension
  • Ability to distinguish a demo from a representative test
  • Ability to assign appropriate authority
  • Initial confidence

During

  • Quality of workflow decomposition
  • Whether participants record a prediction before seeing outputs
  • Quality of acceptance criteria
  • Recognition of missing evidence
  • Peer-challenge quality

After

  • Completed Frontier Fit Map
  • Representative test design
  • Operating-mode decision
  • Accountable human
  • Escalation condition
  • Stop rule
  • Seven-day experiment

Later

  • 7 days: first representative case run, what changed, evidence generated, plan advanced or stopped
  • 30 days: tasks tested, controlled pilots started, critical errors and near misses, cycle-time and quality change versus baseline, share of pilots with owners and stop rules
  • 90 days: sustained use only for tasks that passed criteria, workflow-related business outcomes, drift and override patterns, independent transfer to a new task

The 15-point post-performance rubric

Five criteria, scored 0–3. A workbook that names a department rather than a task, or a success metric rather than a stop rule, cannot reach the top band.

Assessment rubric: five criteria scored from 0 to 3 points
Criterion0 points1 point2 points3 points
Task decompositionJob/department namedOne broad activityMultiple tasks but unclear boundaries4–7 observable tasks with inputs, outputs, decisions, owners
Frontier hypothesisNo rationalePreference-based rationaleSome task cuesEvidence-based rationale with uncertainty explicitly stated
Test designDemo onlyUnrepresentative case or no baselineBaseline plus typical casesSame rubric, credible baseline, 3–5 representative cases including edge case
Authority and guardrail“Human checks”Human named but check unclearEvidence source or escalation namedAccountable human, independent evidence, escalation and stop rule
Metrics and actionVanity/activity metricTime or volume onlyQuality and timeQuality/correctness, time, failure severity, owner, review date, decision rule
Assessment and measurement plan (in the portfolio)

Prototype thresholds. Institutional assessment standards require faculty and program validation.

What counts, and what only looks like it counts

Meaningful measures

  • Rubric gain
  • Test quality
  • Correctness
  • Critical-error rate
  • Decisions revised or stopped
  • Transfer to a new task
  • Business outcome versus baseline

Vanity measures

  • Attendance
  • Slides viewed
  • Prompts submitted
  • AI login volume
  • Raw output volume
  • Satisfaction
  • Self-reported confidence

Satisfaction and self-reported confidence are worth collecting — but neither demonstrates that a decision improved.

Continuous improvement, with a worked example

The revision loop

  1. 01Participant feedback
  2. 02AI-assisted analysis
  3. 03Theme identification
  4. 04Learning-performance data
  5. 05Facilitator observations
  6. 06Recommended revisions
  7. 07Human review
  8. 08Curriculum update
  9. 09Version history

Illustrative cohort of 24

  1. 0118 of 24 participants completed a task map.
  2. 02Only 9 wrote a true stop rule.
  3. 03Feedback revealed confusion between success metrics and stop rules.
  4. 04Facilitator notes showed the demonstration ran too long.
  5. 05Satisfaction was high, but satisfaction did not change the diagnosis.
  6. 06Proposed revision: shorten the demo, add a stop-rule counterexample, move the stop-rule field, and add a facilitator checkpoint.
  7. 07Validate the revision by comparing stop-rule rubric scores in the next cohort.

Illustrative data created to demonstrate the analysis and revision process. No cohort has been delivered.

09 — AI-enabled production

AI accelerated the work. It did not decide what the research means.

The same discipline the workshop teaches executives governs how the workshop itself was produced: AI holds speed, humans hold judgment and authority.

Production pipeline

  1. 01Faculty research
  2. 02Research ingestion
  3. 03Evidence extraction
  4. 04Claim ledger
  5. 05Learning-objective generation
  6. 06Instructional architecture
  7. 07Faculty / SME validation
  8. 08Workshop production
  9. 09Deck + workbook + facilitator guide + exercises
  10. 10Cross-asset QA
  11. 11Delivery
  12. 12Assessment
  13. 13Feedback analysis
  14. 14Human review
  15. 15Versioned revision

AI accelerated

  • Initial source extraction
  • Cross-document comparison
  • Candidate research summaries
  • Learning-objective alternatives
  • First-draft scenarios
  • Asset transformation
  • Consistency checking
  • Readability review
  • Accessibility review support
  • Feedback clustering
  • Change-summary drafting
  • Version comparison
  • Repetitive formatting and production work

Humans remained responsible for

  • Determining what the research actually means
  • Separating findings from speculation
  • Approving executive implications
  • Selecting the learning capability
  • Making pedagogical tradeoffs
  • Protecting nuance and limitations
  • Judging ethical and organizational consequences
  • Validating realism
  • Facilitating the experience
  • Interpreting learner-performance data
  • Approving release
  • Deciding whether curriculum should change

Research-integrity controls

Speed is worthless if the research is misrepresented. Eight controls sit in the workflow as hard requirements, not preferences.

  • 01Every factual claim traces to a source
  • 02AI cannot invent or repair missing citations
  • 03Causal language cannot exceed the original study
  • 04Findings remain separate from implications
  • 05Prototype implications are labeled
  • 06Faculty approval is required before institutional use
  • 07Confidential participant or organizational data is excluded from public AI tools
  • 08All released assets require human QA

The prompt library included in the package is safeguarded: it excludes confidential data and cannot be used to generate citations.

10 — Inclusive design

Twenty accessibility and inclusion decisions

Executive audiences differ in technical background, authority, bandwidth, confidentiality constraints, and comfort speaking in a room. Each decision below removes a barrier to participating fully.

  • Plain-language explanations for nontechnical executives
  • No requirement to write code
  • Examples drawn from multiple organizational functions
  • Definitions available at first use
  • Color never carries meaning alone
  • High-contrast typography
  • Minimum readable slide type
  • Accessible document heading structure
  • Repeating table headers
  • Descriptive links
  • Keyboard-accessible website interactions
  • Reduced-motion support
  • Printable and digital workbook options
  • Low-bandwidth and offline alternatives
  • Prepared demonstration output if live AI fails
  • Individual reflection before public discussion
  • Anonymous question option
  • Low-risk sample workflow for participants who cannot use confidential work
  • Explicit distinction between AI fluency and professional intelligence
  • No assumption of equal access, authority, technology, or AI experience

This website applies the same standards: semantic structure, keyboard-accessible controls, contrast that does not depend on color alone, reduced-motion support, and downloadable alternatives to every interactive element.

11 — The artifacts

A complete, connected production system

Every asset exists because a specific person needs it at a specific moment: the facilitator before and during delivery, the participant during and after, and the learning team afterwards.

Download the complete package (ZIP download)9 files · all documents in one archive

Independent candidate prototype created using publicly available HBS research. Not an official Harvard Business School product.

Facilitator system

  • PPTX · 24 slides

    Executive workshop deck

    Facilitator, projected to participants

    The primary facilitation deck for the 60-minute session: provocation, study design, inside- and outside-frontier findings, limitations, the Frontier Fit Loop, live demonstration, participant exercise, peer challenge, debrief, and seven-day commitment. Includes facilitator notes and per-slide source blocks.

    Facilitation assetsResearch fidelityExperiential sequencing

  • PDF · 19 pages

    Facilitator guide and SOP

    Facilitator, learning-operations team

    Makes the experience deliverable and repeatable: minute-by-minute plan, room and virtual setup, SAY/ASK/DO/WATCH FOR/DEBRIEF language, transitions, expected responses, misconceptions, difficult questions, technology contingencies, accessibility considerations, assessments, follow-up system, production SOP, and safeguarded prompt library.

    Delivery supportAI-enabled productionInclusive deliveryVersion control

Participant system

  • PDF · 14 pages

    Participant workbook

    Participants (executives and managers)

    The active participant tool — not a printed copy of the slides. Participants select a real workflow, decompose it into observable tasks, predict AI fit, design a representative test, assign authority, define a stop rule, critique a peer's plan, and build a seven-day experiment. Includes a completed B2B example and the application rubric.

    Participant-centered formatsExperiential learningAssessment design

  • PDF · 1 page

    Executive takeaway card

    Participants after the session

    The one-page takeaway: the Frontier Fit Loop, AI-led / human–AI / human-led operating modes, signals that should not justify scaling, and the participant's seven-day experiment.

    Transfer designParticipant-centered formats

Overview and design record

  • PPTX · 7 slides

    Concise interview presentation

    Interview panel

    A seven-slide, five-to-seven-minute overview of the challenge, selected research, learning objective, participant exercise, AI production system, measurement strategy, and faculty-validation plan. This is not the participant workshop.

    Stakeholder communicationNarrative clarity

  • PDF · 39 pages

    Complete research and design portfolio

    Hiring manager, faculty reviewer, instructional-design leader

    The intellectual source of truth: role analysis, research landscape and scoring, faculty research brief, personas, objectives, learning architecture, workshop specification, assessment and feedback systems, AI-enabled production workflow, SOP and prompt library, accessibility review, source ledger, and quality audit.

    Research translationBackward designQuality assuranceSource discipline

Independent prototype artifacts. Not Harvard Business School materials and not endorsed, reviewed, or approved by HBS or the HBS AI Institute. Faculty validation would be required before any institutional use.

Download every document as a single archive

12 — Honesty and validation

What is publicly supported, and what requires faculty validation

Naming the boundary is part of the discipline this project teaches. A polished document is not evidence, and an instructional translation is not a research finding.

Publicly supported

  • The research question
  • Study design
  • Sample
  • Experimental conditions
  • Reported findings
  • Research limitations
  • Current public job responsibilities
  • Public HBS AI Institute learning priorities

Requires faculty and institutional validation

  • The Frontier Fit Loop as the preferred instructional translation
  • Executive implications
  • Terminology
  • Scenario realism
  • Acceptable degree of simplification
  • The operating-mode decision rules
  • Assessment thresholds
  • Transfer measures
  • Facilitator guidance for difficult questions
  • Fit with existing HBS programming
  • Market positioning
  • Institutional accessibility standards
  • Data-governance requirements
  • Faculty attribution language

Nothing in this project is a Harvard Business School product. It is an independent demonstration of a process — and the process includes knowing which claims are not yet mine to make.

Role capability → evidence

Twelve capabilities named in the role specification, and where each one is demonstrated in this project.

Role capabilities mapped to the evidence in this project
CapabilityEvidence
Faculty and SME partnershipFaculty research brief, approval gates, validation questions
End-to-end learning developmentResearch intake through delivery, assessment, revision, and archive
Research translationStudy findings transformed into an executive decision problem and experiential framework
Experiential learningReal-work Frontier Fit Map, live demonstration, peer challenge, seven-day experiment
Facilitation assetsComplete deck, speaker notes, facilitator guide, misconceptions, contingencies
Participant-centered formatsWorkbook, executive card, digital companion specification
Digital and multimedia learningVideo script, infographic architecture, interactive companion specification
AI-enabled productionWorkflow, human/AI responsibility matrix, SOP, safeguarded prompt library
MeasurementBaseline, formative checks, post-performance rubric, transfer measures
Continuous improvementFeedback instrument, analysis pipeline, revision example, version history
Quality assuranceClaim ledger, source blocks, accessibility audit, slide-overflow test, release controls
In-person and virtual readinessRoom and virtual setup, low-tech fallback, backup demo, inclusive participation

13 — About this project

Why I built this instead of only describing it

I am Amir Daniel, an instructional designer working at the intersection of research translation, experiential learning, and AI-enabled production. I built this project independently, in a few focused hours, because the most honest way to show how I would approach the HBS AI Institute Instructional Designer role was to actually do the work — select the research, design the experience, produce every supporting asset, define the measurement, and mark the limits.

The judgment I want to demonstrate is not that I can generate documents quickly. It is that I can decide what a study does and does not support, design a capability worth building, and keep human authority over every claim an executive audience would carry back into their organisation.

What I would do first with faculty

  1. 01Confirm which findings may be stated, and in what language.
  2. 02Validate the Frontier Fit Loop as an acceptable instructional translation.
  3. 03Test the demonstration scenario for realism with a subject-matter expert.
  4. 04Agree the assessment thresholds and transfer measures with the program team.
  5. 05Pilot with one cohort and revise from rubric data, not satisfaction scores.