Explore

Alithea Plan Worksheet

⁠

Alithea Growth Wedge Plan Template (30 / 60 / 90 / 365)

0) Plan header + lanes map (use these IDs throughout)

Subject: ☐ Alithea (org plan) ☐ Me (engagement plan) ☐ Dual (recommended)

Primary wedge (choose 1):

L-A Ops Backbone MVP (recommended)

L-B Archive + Permissions Sprint

L-C Applied Partnerships Pilot (e.g., WSU/Shocker Studios)

L-X Other wedge: __________________________

Lane legend (reference these IDs later)

Core Lanes (pick 1 as primary wedge; others can be secondary):

L-A — Ops Backbone (Invisible Infrastructure) Dashboards, workflows, CRM/ERP-lite, weekly rhythm, handoffs, reporting

L-B — Archive + Authority (Artifacts, Permissions, Stewardship) Artifact intake, metadata, rights/permissions, preservation, advisory circle

L-C — Applied Partnerships (Mocap / XR / Industry / Research pilots) WSU collaboration, mocap training, digital arts curriculum pilots, partner pipeline

Secondary Lanes (optional—explicitly check if “in scope”):

L-D Education Engine (Curriculum + Outcomes)

Workshops, youth programs, school partnerships, measurable outcomes

L-E Embodied Wellness (Somatics-adjacent offerings) Feldenkrais/Laban-informed movement literacy; careful positioning + outcomes

L-F Creative Collaborations (Cross-disciplinary productions) Music/visual art/installation/video collaborations; capture + documentation

L-G Story + Positioning (Narrative + materials) Deck, one-pagers, funder language, partner framing, website language

L-H Funding + Revenue Engine (Grants + Donors + Earned revenue) Grant calendar, submission pipeline, sponsorships, pricing, sales motion

L-I Network Map (People/Alumni/Institutions graph) Stakeholder map, introductions, alumni surveys, advisory board building

Plan owner(s): __________________________

Point person (weekly decisions): __________________________

Decision cadence: ☐ Weekly 30 min ☐ Biweekly 60 min ☐ Other: ________

Constraints (time/budget/staff): __________________________

Definition of done for first wedge: __________________________

Rule: In each section below, label items with the lane ID(s), e.g., [L-A] or [L-B + L-G]. If something doesn’t apply, leave it blank.

⁠

1) North Star + boundaries (so it doesn’t sprawl)

North Star Outcome (1 sentence)

“In 12 months, Alithea has a lightweight operating backbone and a documented ‘movement grammar’ asset base that supports sustainable programs, grants, and partnerships—without increasing admin burden on artists.”

Explicit boundaries (anti-scope-creep)

Not building a huge platform in Year 1

Not chasing “Disney-tier” partnerships without proof assets

Not digitizing everything—start with a curated seed set

Not creating new bureaucracy—minimum viable operations

⁠

2) Workstreams (lane-aligned)

Use 3–5 workstreams max. Recommended by lane:

W1 [L-A] Ops + Systems: dashboard, workflows, handoffs, routines

W2 [L-B] Archive + Permissions: intake, metadata, rights clarity, storage

W3 [L-C + L-H] Pipeline: partners + grants tracking, outreach queue

W4 [L-D / L-C] Offer Ladder: workshops → pilots → repeatables

W5 [L-G] Narrative: positioning, materials, proof story, deck/one-pagers

(If you want minimalism: W1 + W3 only.)

⁠

3) 30-day plan (Discovery + MVP wedge)

Objectives (pick 2–3, label lanes)

[L-A] Establish single source of truth for people/partners/grants/works/artifacts

[L-A] Ship an Operating Dashboard + weekly rhythm + next actions

[L-B] Define artifact intake + permissions tracking (start with 10 items)

[L-G] Produce 1-page positioning narrative + talk track v1

[L-C] Identify one pilot partner + draft pilot outline

Deliverables (lane-tagged)

D1 [L-A]: Minimal data model (tables + required fields)

D2 [L-A]: Dashboard (5 widgets max)

D3 [L-B]: Artifact intake form + permission status field + tagging rules

D4 [L-A + L-H]: Grant/partner tracker + outreach queue

D5 [L-G]: One-page narrative + “what we do / why now / what’s next”

Success metrics

[L-A] % key contacts captured: ___ / ___

[L-H] # grants tracked w/ deadline + next action: ___

[L-B] # artifacts ingested w/ permissions status: ___

Weekly review held? ☐ yes ☐ no

Risks + mitigations

[L-A] time scarcity → “2-hour/week mode” + strict scope

[L-B] messy files → intake-first; don’t reorganize everything

[All] unclear ownership → name point person + decision cadence

⁠

4) 60-day plan (Proof assets + first external pilot)

Objectives

☐ [L-A] Expand data coverage + reliability

☐ [L-B + L-G] Movement Grammar prototype (taxonomy + examples)

☐ [L-C] Launch 1 pilot (WSU workshop or similar)

☐ [L-H] Grant pipeline live (calendar + templates + checklist)

Deliverables

D6 [L-B]: Movement Grammar v0.1 (10 exercises/works tagged w/ 8–12 attributes)

D7 [L-C + L-G]: Pilot package (one-page offer + agenda + outcomes + capture plan)

D8 [L-H]: Grant pipeline doc (list + deadlines + templates + checklist)

D9 [L-I]: Partner map (20 nodes + who-introduces-who + next action)

Success metrics

[L-C] Pilot scheduled? ☐ yes ☐ no

[L-B] # movement grammar entries: ___

[L-H] # active grant submissions in motion: ___

[L-I] # warm intros requested/secured: ___

⁠

5) 90-day plan (Productization + repeatability)

Objectives

☐ [L-D/L-C] Convert pilot into a repeatable offering (curriculum + pricing + deck)

☐ [L-B] Improve archive process (permissions clarity, capture standards)

☐ [L-A] Reduce operational friction (handoffs, tasks, comms templates)

☐ [L-G] Publish proof story for funders/partners (metrics + narrative)

Deliverables

D10 [L-D + L-C]: Offer ladder v1 (workshops → residencies → mocap training → archive releases)

D11 [L-B]: Content capture kit (release form, shot list, metadata template, storage rules)

D12 [L-G + L-H]: Board/funder update memo (metrics + story + next asks)

D13 [L-A]: Versioned roadmap update + cadence SOP

Success metrics

[L-D/L-C] # repeatable offers packaged: ___

[L-B] # permissions-cleared assets: ___

[L-H] $ pipeline (earned + grants requested): $___

[L-A] scramble reduced (self-report): ___

⁠

6) 365-day plan (Institutionalization + optional expansion)

Strategic outcomes (choose 2–4, lane-tagged)

☐ [L-B] Archive Seed Collection + stewardship plan + advisory circle

☐ [L-C] 1 recurring institutional partnership producing annual work

☐ [L-H] Stable funding calendar + submission rhythm

☐ [L-D] Repeatable education product adopted by 2–3 partners

☐ [L-G] Annual “State of the Work” report (story + metrics)

☐ [L-I] Mature network map + alumni engagement loop

Big deliverables

D14 [L-B + L-G]: Archive initiative page + intake pipeline + advisory circle roster

D15 [L-C]: Partnership playbook (pitch → run → document → repeat)

D16 [L-H]: Funding engine playbook (grants + donors + sponsorship)

D17 [L-A]: Operations handbook (cadence + roles + dashboard SOP)

⁠

7) Engagement modes (if “you” are a subject)

Mode A (Discovery Sprint) [L-A + L-G]: 2–4 weeks → wedge choice + roadmap + dashboard spec

Mode B (Build Sprint) [Primary lane]: 4–8 weeks → MVP shipped + pilot packaged

Mode C (Operator-in-Residence) [All]: 3–6 months → cadence + pipeline + productization

⁠

8) First working session input checklist (tag the lane each item feeds)

[L-A] current programs/offers list + calendar

[L-I] contact lists (donors, alumni, partners)

[L-B] where artifacts/files live + any permission realities

[L-H] grant history + known funders

[All] weekly point person + time constraints

[L-G] what “success in 90 days” should feel like

⁠

Tech Stack

Link⁠

⁠

Nonprofit Credentials (EIN )

Bank Account

Purchase Card

Office & Email

Project Database

Bookkeeping

Communication

AI Chat

Payment Processing

Want to print your doc?
This is not the way.

Try clicking the ··· in the right corner or using a keyboard shortcut (

CtrlP

) instead.