FAKTORY OPS / Manual
Back to dashboard
FAKTORY STUDIOS OPERATING GUIDE

Dashboard Operating Manual

How to capture work, run the business, and keep Faktory Ops trustworthy without turning dashboard maintenance into another job.

Primary rule: capture first, organize later. Never delay recording something important because you do not have time to classify it perfectly.

1. The operating model

Faktory Ops is the operating record for what is happening across Faktory Studios: current work, backlog, experiments, customer evidence, metrics, finances, commitments, decisions, and project health.

CadencePurposeTypical actions
During the dayDo not lose informationUse Universal Capture for ideas, activity, expenses, feedback, metrics, and tasks.
DailyReconcile realityClear captures, scan Attention, confirm non-GitHub activity, and let GitHub/ChatGPT reconciliation update evidenced development work.
WeeklyChoose and learnSet one primary outcome, supporting tasks, review experiments, refresh key metrics, clean backlog.
Monthly / QuarterlyRun the businessReconcile actual revenue/expenses monthly; review portfolio, strategy, positioning, and competitors quarterly.

Trust hierarchy

  • GitHub proves code activity, not human validation or customer publication.
  • A missing metric means unknown, not zero.
  • Recorded financial actuals remain separate from estimates and subscription projections.
  • Human validation and publication are explicit states.

2. Home: the daily command center

Open Home first. It should answer: What deserves attention? and What should I do next?

  • Universal Capture - fastest place to record something before it is forgotten.
  • Review cadence & data freshness - what information is becoming stale.
  • This week's outcome - the result the week is organized around.
  • Next actions - selected work, not the whole backlog.
  • Attention queue - exceptions such as blockers, overdue tasks, stale data, feedback, and experiment reviews.
  • Upcoming commitments - dates that can surprise you if they are not visible.
If Attention becomes noisy, resolve the underlying records rather than learning to ignore the warnings.

3. Universal Capture: your default input

Use Universal Capture whenever something matters but you do not want to interrupt your current work to fill out a full form.

PrefixUse forExample
activity:Something that happenedPosted the ORDO article to X and Bluesky
task:A concrete actionFollow up with the ORDO voucher recipient
idea:A possibility worth preservingAdd a living project map to ORDO
experiment:A test designed to learnTest whether an ORDO Short drives store visits
feedback:Customer evidenceFirst scan feels overwhelming
metric:A measured valueORDO pageviews were 420 this week
expense:Money spentPaid $39 for a Unity plugin
revenue:Money receivedORDO sale posted this month
decision:A choice worth rememberingPause Sideline Atlas until ORDO 1.3 ships

Prefixes are optional. The raw capture remains intact until you convert or archive it.

Conversion

  1. Capture the rough sentence.
  2. Confirm or change the suggested record type.
  3. Select a project if applicable.
  4. Fill only the required facts.
  5. Convert. The structured record is created while the original note is preserved.

4. Weekly planning: focus without losing the backlog

  • Choose one primary outcome.
  • Select a small number of supporting tasks.
  • Estimate hours when it will expose capacity problems.
  • Defer work explicitly instead of pretending everything is active.
  • At week end, record completed, carried forward, or dropped outcomes and lessons.
A strong outcome describes a result. “ORDO 1.3 passes manual release verification” is stronger than “Work on ORDO.”

4A. CEO reviews: preserve the executive view

Use the CEO Reviews tab after the ordinary weekly closeout and for a consolidated monthly rollup. It keeps dated highlights navigable without replacing the underlying tasks, metrics, finances, evidence, or canonical strategy documents.

  • Record the review period and cadence (weekly or monthly).
  • Attach a source period and basis to every key metric.
  • Separate wins, blockers, and opportunities.
  • Close with exactly three priorities.
  • List unavailable or partial data explicitly; missing never means zero.
  • Link the canonical Markdown review under business/ceo-reviews/.

Adding a review

  1. Close the Weekly plan or reconcile the monthly Money scorecard.
  2. Verify source values and preserve mixed periods or gross/net bases separately.
  3. Create the canonical weekly YYYY-MM-DD.md or monthly YYYY-MM.md file from the repository template.
  4. Add the structured mirror through /api/insights?resource=ceo-reviews. Corrections become explicit amendments rather than silent rewrites.
Business boundary: Faktory Studios recommendations stay within the Unity games, courses, and game-developer tools disclosed to and accepted by the owner's employer. Exclude interactive-multimedia consulting that competes with that employer.

5. Backlog, ideas, and outcomes

Tasks

Use tasks for concrete executable work. Use due dates only for real deadlines; use revisit dates for “think about this again later.”

Ideas

Use ideas for possibilities that have not earned execution yet. Move them through exploring, experimenting, adopted, parked, or rejected.

Outcomes

Use outcomes to group tasks around a business result.

Do not turn every thought into a task. An unvalidated possibility should stay an idea.

6. Experiments: turn uncertainty into learning

Use an experiment when you are deliberately testing a belief rather than doing routine work.

FieldQuestion
HypothesisWhat do I believe will happen?
MethodWhat exactly will I do?
Success criteriaWhat would count as evidence in favor?
Stop criteriaWhen should I stop?
Effort/spend limitWhat is my maximum exposure?
Review dateWhen will I evaluate the result?

Example: If an ORDO YouTube Short demonstrates a painful Unity problem and links directly to the Asset Store, it will generate measurable product-page traffic within seven days.

AI may help draft or summarize an experiment. Adopt / park / reject remains a deliberate human decision.

7. Evidence and metrics

Prefer a small number of metrics that change decisions over a large collection of numbers.

  • Create stable metric definitions per project.
  • Log dated observations so trends become visible.
  • Use CSV import when a service exports structured data.
  • Use manual metric capture for one-off measurements.
  • Record source, period/cohort, and caveats when relevant.
  • Never enter zero because data is unavailable.

Data freshness

The freshness panel records whether a source was reviewed. It does not create metric or financial values.

SourceCadence
Non-GitHub activity check-inDaily
Unity Asset Store analyticsWeekly
Kajabi analyticsWeekly
YouTube analyticsWeekly
Social channel metricsWeekly
Revenue and sales actualsMonthly
Expenses and subscriptionsMonthly
Portfolio and strategy reviewQuarterly

8. Money: actuals vs estimates

  • Revenue/expense entries - dated business actuals.
  • Bank imports - reviewed transactions rolled into actuals.
  • Project revenue - current monthly estimate or live synced value.
  • Subscriptions - recurring projected costs.
  • Recorded Actuals - historical actual entries only.
  • Income vs Expenses estimate - revenue estimates vs normalized subscription costs.
Quick-capture unusual purchases you might forget, then use monthly bank reconciliation as the authoritative check. Avoid duplicate entry.

9. Activity, project pages, commitments, and decisions

Activity

Log feature-level shipped / next / blocked / note updates. Avoid commit-level noise.

Project pages

Use the project page to understand current status, notes, release/validation facts, GitHub evidence, updates, links, and project metrics.

Commitments

Use commitments for dated obligations not already represented by a task due date, release date, experiment review, or subscription renewal.

Decisions

Record choices likely to be re-litigated later. Capture rationale, tradeoffs, evidence to revisit, and review date when useful.

10. Working with ChatGPT and other agents

  • ChatGPT can reconcile GitHub activity with dashboard state and write high-confidence updates with source=chatgpt.
  • You can say “Capture this for Faktory: ...” instead of opening the dashboard.
  • Development evidence can often be reconciled automatically.
  • Metrics, money, human validation, publication, experiment decisions, and strategy should only change when evidence is direct.
  • If sources conflict, surface and reconcile the conflict instead of silently choosing one.

11. Recommended routine

Daily - 3 to 5 minutes

  1. Open Home.
  2. Capture anything GitHub cannot know.
  3. Triage the capture inbox.
  4. Scan Attention.
  5. Confirm the non-GitHub activity check-in.
  6. Let daily ChatGPT reconciliation handle evidenced development changes.

Weekly - 15 to 30 minutes

  1. Review last week's outcome and lessons.
  2. Set one primary outcome and supporting tasks.
  3. Review experiments due soon.
  4. Refresh weekly metric sources.
  5. Clean stale backlog items.
  6. Review the next two weeks of commitments.
  7. Publish the verified weekly CEO highlights and three priorities.

Monthly - 30 to 60 minutes

  1. Import/review bank data.
  2. Confirm revenue and sales actuals.
  3. Review scorecard vs targets.
  4. Review subscriptions.
  5. Inspect metric trends.
  6. Publish the monthly CEO rollup only after reconciliation; list any missing sources.

Quarterly - 60 to 90 minutes

  1. Review the portfolio.
  2. Review product positioning and competitors.
  3. Evaluate experiments and customer evidence.
  4. Decide what to continue, pause, or invest in.
  5. Update strategic decisions and next-quarter outcomes.

12. Quick reference: where does this go?

I have...Put it in...
A rough thought I may forgetUniversal Capture
A concrete actionBacklog Task
A possible directionIdea
A testable beliefExperiment
Something shipped, blocked, or learnedActivity Update
Customer evidenceFeedback
A number measured on a dateMetric Observation
Money received or spentRevenue / Expense
A hard date or obligationCommitment or Task Due Date
A choice worth rememberingDecision
Work selected for this weekWeekly Plan
Verified executive highlights and next prioritiesCanonical CEO review + CEO Reviews tab
Something requiring interventionAttention Queue (generated from the underlying record)
One rule to remember: if you catch yourself thinking “I'll remember to add that later,” put the rough sentence into Universal Capture immediately.