クイック回答

first 90 daysを3 vague impressionでなく3 review boundaryで設計。day30までにrole outcome、accessible orientation、least privilege、safe evidence checkpoint。day60までにbounded contribution、accountable handoff、two-way correction、role-relevant learning。day90までにdefined ownership、role-map evidence review、sustainable cadence、next-quarter handoff。各itemにowner、evidence、support、authority、review date、exception pathが必要。

day one前にplan contractを定義

scope/role version

start date、employment/location context、role version、essential duty、manager、trainer、system、work setting、schedule、plan非decision範囲を記録。

outcome/evidence schema

各outcomeにjob reason、expected artifact/behavior、evidence source、acceptance owner、quality/control criteria、dependency、contrary evidence、statusを定義。

support/time/access

required training、paid-time treatment、accessible format、accommodation route、equipment、data、least privilege、reviewer availability、fallback、manager commitmentを明示。

review/decision right

checkpoint、employee comment/correction、evidence state、scope change、access grant、work acceptance、conflict adjudication、employment rule、unsafe stopの権限を定義。

day 1–30：orient・enable・safe access verify

first boundaryはorganizationがworkをunderstandable/accessibleにしたかを確認し、system、policy context、relationship、support前にfull outputを要求しない。

30.1

role/outcome map

managerとemployeeがessential duty、first-quarter priority、dependency、decision right、done evidenceを確認。

acceptance evidence
confirmed role map、named owner、question/conflict log。
guardrail
speed、social fluency、after-hours availability、team similarityをcapability proxyにしない。
30.2

accessible orientation/policy access

required policy、conduct、safety、benefit、privacy notice、accommodation processをaccessible formatで提供し質問時間を確保。

acceptance evidence
delivery/access確認、question route、receiptとcomprehension分離。
guardrail
click/signatureはunderstanding、unrelated processing consent、training successの証明ではない。
30.3

least-privilege tool/safe practice

roleに必要なaccount、data、environment、approvalのみ付与しproduction前にsandbox/reversible pathでtraining。

acceptance evidence
access owner、approval、scope、expiry、test evidence、exception routeを記録。
guardrail
convenienceでbroad accessを与えずdefault tool都合でeffective accommodationを拒否しない。
30.4

first evidence checkpoint

small representative taskでinstruction clarity、access、dependency、support need、safetyを確認しemployeeをlabel化しない。

acceptance evidence
task context、question、observed output、blocker、feedback、correction、next supportを記録。
guardrail
one early task、attendance、accent、disability、manager impressionをperformance forecastにしない。

day 31–60：evidence/correction付きcontribution

second boundaryはguided practiceからbounded real workへ移行。scope/controlを明示しemployeeだけでなくwork systemもreview。

60.1

bounded guided contribution

real but bounded deliverableにcustomer、quality、security、approval、escalation expectationを事前定義。

acceptance evidence
accepted brief、checkpoint、cited work evidence、review comment、approved release/safe rollback。
guardrail
visible activity、message volume、office presence、unreviewed AI outputだけでcontributionを測らない。
60.2

stakeholder/handoff map

actual dependency role間でacceptance/exception ownershipを含むaccountable handoffを実践。

acceptance evidence
sender、receiver、required context、acceptance evidence、unresolved risk、due point、escalation owner可視化。
guardrail
new employeeにunclear ownership修復やauthority/resourceなしworkを押し付けない。
60.3

feedback/correction/manager duty

two-way reviewでexpected/observed evidence比較、record correction、manager/system blocker特定、support合意。

acceptance evidence
evidence citation、employee response、correction、owner、due、follow-up test保持。
guardrail
feedbackはpersonality verdictでなくmissing training、inaccessible system、conflicting instructionをemployee weaknessにしない。
60.4

role-relevant learning demonstration

realistic condition/approved supportでpriority workflowをexplain、perform、document、teach-back。

acceptance evidence
relevant artifact、control use、question、verification、uncertainty、recovery evidence取得。
guardrail
course completion、quiz score、confidence、memorized policyを十分なjob performance evidenceにしない。

day 61–90：accountable ownership test/handoff

third boundaryはrealistic authority/supportでdefined outcomeをtestしnormal operating cadenceへ移行。day90はautomatic pass/failやproductivity proofではない。

90.1

accountable ownership trial

defined outcomeをexplicit authority、dependency、review gate、fallback、irreversible decisionのhuman owner付きで委任。

acceptance evidence
plan、decision、evidence、approval、exception、handoff、accepted output、retrospectiveをlink。
guardrail
ownershipはunsupported autonomy、unlimited hours、hidden risk、speed目的のcontrol bypassではない。
90.2

role mapに対するoutcome review

agreed outcome/control evidenceとpriority change、manager commitment、accommodation effectiveness、blocked dependencyをreview。

acceptance evidence
criterion state、cited/contrary evidence、employee comment、adjudicated next actionを記録。
guardrail
result後にstandardをreverse-engineerせずscope/support/time/accessが異なる人を比較しない。
90.3

sustainable operating agreement

recurring 1:1、decision/escalation route、work/communication norm、development support、access review、backup、correction channelを合意。

acceptance evidence
cadence、owner、response expectation、accessible channel、record、review date確認。
guardrail
sustainabilityをconstant availability、surveillance、synchronous presence、disagreement suppressionと同一視しない。
90.4

plan closeout/next-quarter handoff

completed item close、unresolved risk+owner carry-forward、unneeded access removal、owed support記録、next-quarter outcome plan作成。

acceptance evidence
accepted item、open issue、access change、lesson、commitment、notice、next review保持。
guardrail
day 90はreview boundaryでありfit、productivity、retention、compliance、all learning completionの証明ではない。

worked example：missed checkpointはautomatic employee failureではない

hypotheticalでreal employee/performance resultではない。new operations analystがday60 dashboardをmiss。shallow reviewはslow ramp/weak ownershipと記すがproduction accessは12 working day遅延、metric definitionは2回変更、reviewer unavailable。employeeはsandbox版、conflict記録、required approval requestを完了。

incorrect conclusion

calendar varianceをpersonal underperformanceとしmissing organizational inputを消しstandardを後変更している。

evidence-based correction

statusはblocked dependencyでaccepted/failedではない。original due、access request/grant date、definition version、sandbox artifact、approval request、reviewer absenceを保持。managerがaccess/metric resolutionをownしinput ready後にnew evidence checkpoint。employment actionはAI labelでなくauthorized process。

OpenMaxによる90-day plan coordination

OpenMaxはapproved role-plan version、preboarding dependency、accessible material、least-privilege request、training schedule、milestone evidence、manager/employee check-in、blocked alert、feedback/correction、review assignment、access recertification、exception route、next-quarter handoffをcoordinate。employment classification、pay、job design、legal scope、accommodation、sensitive data、access authority、performance standard、dispute、employment decisionはhuman。

before startrole、support、access、legal review
day 30orientation、safe access、first evidence
day 60contribution、handoff、correction
day 90ownership、review、next-quarter plan

source・legal boundary・limitation

qualified local counselおよびHR、wage/hour、benefit、accessibility、privacy、security、labor、performance ownerが適合化する。required job-related trainingはfacts/lawによりcompensable、accommodationはindividualized、accessはassigned taskに必要な範囲、protected trait/proxyはopportunity/support/evaluationへ影響させない。plan completion、manager click、AI summary、activity metric、day90 statusをunderstanding、fit、productivity、compliance、retention、fairnessの証明にしない。

editorial method/scope OpenMax編集部はprimary materialを確認しplan contract、12 outcome、blocked-dependency caseを独自構成。2026年9月3日再確認。OPMはU.S. federal practice、DOLはhealth-care example、EEOCはU.S.-specific、NIST controlはdefined scope。sourceはtemplate validation、OpenMax endorsement、employee data、result保証なし。

よくある質問

全roleでsame milestone？

no。governance fieldはconsistentにしoutcome、evidence、support、access、timing、acceptanceはactual role/lawful processから導く。

day90でsuccessful onboardingを証明？

no。review boundaryでありevidence、missing input、priority change、accommodation、employee comment、manager obligation、downstream outcomeを継続確認。

mandatory onboarding trainingはafter hours？

unpaidと仮定しない。wage/hour ruleはfacts/jurisdictionによるためqualified local ownerがclassification、schedule、time recordを行う。

access/manager supportが遅れたら？

blocked dependencyを記録しdate/evidence保持、organizational owner指定、approved processのみで調整しemployee failureへ書き換えない。

OpenMaxで何をautomate？

plan version、dependency、access request、material、checkpoint、evidence、correction、review、handoffをcoordinateしlegal、accommodation、performance、access、employment authorityはhuman。