The Comprehensive Guideline

Set up, run, and master the operating system.

From first login to a fully running weekly rhythm — how WorkFlow thinks, who does what, the 30-day rollout, and how to run every surface well.

For owners, leaders, facilitators & membersVersion 1.0 · July 2026

Part 1

Foundations — what WorkFlow is and how it thinks

1.1 What WorkFlow is

WorkFlow is a company operating system — one connected workspace for the company’s numbers (Scorecards), quarterly priorities (Rocks), problems (Issues), planned work (Projects), daily tasks (My Work and Team Work), communication (Channels), and the weekly WorkFlow Syncs Meeting.

It is built for scaling companies with multiple branches, units, or departments, where the leadership team can no longer see everything by walking the floor. The system replaces scattered tools with one structure, one vocabulary, and one weekly rhythm.

1.2 The six principles

Principle	What it means in practice
Truth before activity	Missing entries, red Scorecards, overdue tasks, and off-track Rocks are surfaced first. Look at problems before celebrating activity.
Ownership over ambiguity	Every work object has one owner, a due date, and a status. Shared ownership is no ownership.
Personal work first	My Work is every member’s home page. If it isn’t in someone’s queue, it won’t get done.
Leadership by exception	Leaders review what the dashboard flags — not every row. Trust the system to surface what matters.
Context stays attached	Files, chats, decisions, and meeting records live with the work they explain.
One operating language	Scorecards, Rocks, Issues, Projects, My Work, Team Work, and the WorkFlow Syncs Meeting mean the same thing to everyone.

1.3 The four levels of the cascade

Level	Sets / owns	Example
1 · Company / HQ	Company Rocks, company health, cross-unit attention	Grow enrollment 40% this quarter.
2 · Business Unit	Unit Rocks, unit Scorecards, unit meeting rhythm	Yangon campus: add 80 new students.
3 · Department	Department goals, Scorecard ownership, member grouping	Book 120 consultations, convert 80.
4 · Individual	Daily tasks, personal Scorecards, owned Rocks	Call 15 leads. Update my Scorecard.

Part 2

Roles and Responsibilities

Six roles cover the whole system. Each role has a clear scope and a small set of duties that must never be skipped.

Role	Scope	System responsibility
Owner	Company	Highest control: units, members, roles, settings, and danger-zone actions.
Admin	Company / workspace	Setup, member management, roles, departments, settings, and audit areas.
HQ Lead	Company	Company-wide execution: branch visibility, Scorecards, Rocks, Issues, and escalation.
Branch Lead	Unit	Local operating control and the branch’s WorkFlow Syncs Meeting.
Team Lead	Department / team	Daily work assignment, project execution, issue handling, and work status.
Member	Self + visible workspace	Own queue, assigned tasks, personal Scorecards, and raising issues.

2.1 Non-negotiables by role

Every Member

✓Start every workday in My Work and update statuses as they change.
✓Score personal Scorecards before the weekly meeting.
✓Raise an Issue the moment you are blocked.

Every Team Lead

✓Assign short daily actions through Team Work.
✓Keep project tasks and daily tasks separate.
✓Check the team’s overdue list daily.

Every Branch Lead

✓Run the Syncs Meeting every week, same day and time.
✓Ensure every Scorecard has a current entry.
✓Keep unit Rocks statused honestly.

HQ Leads and Owners

✓Review the Company Hub weekly.
✓Lead by exception and intervene where risk is flagged.
✓Protect the shared operating vocabulary.

Part 3

Implementation: The 30-Day Rollout

A company comes alive inside WorkFlow in four weeks. Do the phases in order — each one depends on the last.

Week 1 — Structure

1Create the organization and set the Owner account.
2Create business units or branches that mirror how the company really operates.
3Create departments where they add clarity; skip them in small units.
4Invite members and assign roles and departments.

Week 2 — Truth (Scorecards)

1Define 5–15 Scorecards per unit.
2Assign exactly one owner per Scorecard.
3Set targets and direction so status colors mean the same thing everywhere.
4Run two practice weeks of scoring before treating the colors as truth.

Week 3 — Priorities (Rocks) and Work

1Set quarterly Rocks at company level first, then unit level.
2Create Projects for structured, multi-step execution.
3Use Team Work for short daily assignments and coach members to live in My Work.

Week 4 — Rhythm (the Meeting)

1Schedule one weekly WorkFlow Syncs Meeting per unit.
2Run the first live meeting using the guided flow, timers, and standing agenda.
3Rate every meeting and review the trend monthly.

Part 4

The Surfaces: A Working Guide to Every Page

Nine surfaces share the same facts. Update a number or status once and the change flows to every relevant view.

4.1 Company Hub

✓Scan unit health cards first.
✓Compare branches to spot patterns.
✓Work the executive attention queue.

4.2 Scoreboard

✓Shows owner, target, status, current week, and trend.
✓Group metrics by department where useful.
✓Treat a missing entry as seriously as a red one.

4.3 Rocks

✓Each Rock carries one owner, status, and ship date.
✓Off-track Rocks surface upward automatically.
✓Link Rocks to the Scorecards they should move.

4.4 Issues

✓Write the problem, not a pre-baked solution.
✓Vote before the meeting.
✓Record root cause and resolution through IDS.

4.5 Projects

✓Use Projects for planned work across multiple steps.
✓Work exception views: at risk, needs update, and overdue.
✓Treat “needs update” as a health signal.

4.6 My Work

✓One personal queue holds daily and project tasks.
✓Start the day on Today, then check Overdue.
✓Update personal Scorecards here.

4.7 Team Work

✓Use it for short daily actions only.
✓Every assignment needs a clear owner and date.

4.8 Syncs Meeting hub

✓The live path provides the guided flow and timers.
✓The review log keeps every meeting state and record.

4.9 Channels, Notifications, and Context Files

✓Keep conversation attached to work.
✓Use notifications as the attention feed.
✓Attach files and links where their context lives.

Part 5

Scorecard Guidelines

5.1 What makes a good Scorecard

✓Weekly and countable. If it can only be measured monthly, it will only be managed monthly.
✓Activity-based where possible. Leading numbers move before lagging outcomes.
✓One owner. The owner enters the number and answers for it.
✓A target and a direction. Every number needs a clear line between on target and off track.
✓Honest by design. Prefer numbers pulled from real records.

5.2 How many, and which

✓Per unit: 5–15 Scorecards. Per department: 2–5.
✓Cover the engine of the business: demand, conversion, delivery, quality, cash, and people.

5.3 Reading the board

Status	What it means — and what to do
On Target	The number met its target. No meeting time needed.
Watch	Close to the line or trending the wrong way. Worth monitoring.
Off Track	Missed the target. Automatically worth a conversation.
Missing	Not scored. Treat as a discipline issue, not a data point.

Part 6

Rocks Guidelines

6.1 Setting Rocks

✓Three to five per level, per quarter. More than five means nothing is a priority.
✓Specific and finishable. “Improve marketing” is a wish; a shipped outcome is a Rock.
✓One owner, one ship date.
✓Cascaded, not copied. Unit Rocks make company Rocks concrete locally.
✓Connected to the Scorecards they should move and the Projects that deliver them.

6.2 Running Rocks through the quarter

✓Status every Rock weekly: on track or off track.
✓Surface off-track Rocks upward immediately and create an Issue when help is needed.
✓At quarter end, score every Rock done or not done, learn, and reset.

Part 7

Issues and IDS

7.1 The issues list as a company asset

The Issues list is the shared backlog of obstacles, risks, questions, and decisions that need the team’s attention. A healthy list makes problems visible early.

7.2 Raising issues well

✓State the problem in one line, with evidence.
✓Do not pre-bake the solution into the title.
✓Vote before the meeting. Voting sets the order, not the answer.

7.3 Running IDS

Step	How to run it
Identify	Ask “what is the real problem?” until the room agrees on the root cause.
Discuss	Everyone says their piece once. No repeating, politics, or side trails.
Solve	Agree one action, one owner, and one date. Record the decision.

Part 8

The WorkFlow Syncs Meeting: Facilitation Guide

8.1 The standing agenda (90 minutes)

Segment	Time	Purpose
Check-in & wins	5 min	Attendance and one good thing each.
Scoreboard review	15 min	Read statuses; move explanations to Issues.
Rock status	10 min	Each owner gives status in one sentence.
IDS — issues list	55 min	Work top-voted issues to root cause and resolution.
Conclude & rate	5 min	Recap tasks and owners, then rate the meeting.

8.2 Facilitator rules

✓Same day, same time, every week. Start on time.
✓Numbers first, explanations second.
✓Use the built-in timers and move on when time is called.
✓Facilitate, do not dominate.
✓End with clarity: every solved issue produces an owner and date.

8.3 Reading the ratings

✓A healthy meeting averages 8+. Below 7, ask the room what must change.
✓Low ratings usually mean too much reporting, weak IDS, poor preparation, or unclear actions.

Part 9

The Operating Calendar

Cadence	What happens
Daily	Members work from My Work; Team Leads assign through Team Work; statuses stay current.
Weekly	Scorecards are scored, Rocks statused, Issues voted, and the Syncs Meeting is held.
Monthly	Leads review project health, meeting ratings, and persistent exceptions.
Quarterly	Score Rocks, set the next quarter, and refresh Scorecards and Projects.
Yearly	Revisit structure, roles, operating metrics, and long-range company direction.

Part 10

Best Practices, Common Mistakes, and Health Checks

10.1 Best practices

✓Cascade messages after every meeting.
✓Praise in the numbers when a Scorecard improves.
✓Onboard new members through My Work first.
✓Keep the vocabulary pure across every team.

10.2 Common mistakes

Mistake	Correction
Scoring during the meeting	Enter numbers before the meeting; use meeting time to understand exceptions.
Rocks that are projects or wishes	Make the Rock an outcome with a date; deliver it through a Project.
Solving issues in chat	Use chat for coordination and IDS for decisions.
Everything marked urgent	Team Work is for small daily actions; chronic urgency signals weak planning.
Leaders reading every row	Trust exception views and inspect only what needs attention.
Skipping meetings when busy	Busy weeks are exactly when the rhythm pays for itself.

10.3 Monthly health check

1Was the Syncs Meeting held every week, on time?
2Were all Scorecards scored with zero missing entries?
3Does every Rock have a current, honest status?
4Did every solved issue produce an owner and due date?
5Is the overdue list shrinking?
6Are members starting their day in My Work?
7Are decisions being made in IDS instead of chat?
8Is any Scorecard red or missing for three-plus weeks without an Issue?
9Is the meeting rating average 8 or above?
10Could a new leader understand the company’s state from WorkFlow alone?

Appendix A

Vocabulary Standard

Term	Meaning in the system
Scorecard	A weekly tracked number with owner, target, direction, and status.
Rocks	Quarterly priorities with owner, status, due date, and connections.
Issues	Obstacles, questions, risks, or decisions that need IDS.
Projects	Structured execution plans with owned, dated work.
My Work	The member’s personal execution queue.
Team Work	The leader-managed daily task assignment surface.
WorkFlow Syncs Meeting	The team meeting workspace and meeting history.
Company Hub	The HQ view for unit health and leadership attention.
Context files	Files and links attached where their work context lives.
IDS	Identify, Discuss, Solve — the method for turning issues into action.

Appendix B

Quick-Reference Checklists

Member — daily (5 minutes)

✓Open My Work → clear Today → check Overdue → update statuses.

Scorecard owner — weekly

✓Enter this week’s value → confirm status color → add context if needed.

Facilitator — weekly

✓Confirm zero missing entries, check Rock statuses, review votes, run the agenda, and record ratings.

Leadership — weekly (15 minutes)

✓Company Hub → unit health → red Scorecards → off-track Rocks → attention queue.

Everyone — quarterly

✓Score the quarter’s Rocks → set the next quarter → refresh Projects and Scorecards.