Skip to content
Tallyfy
Developers

EOS integration and process component support

Tallyfy and the EOS Process Component

Section titled “Tallyfy and the EOS Process Component”

Tallyfy runs the Process Component of EOS (Entrepreneurial Operating System) day to day. You turn each documented process into a Tallyfy template, launch it whenever that work starts, and every task in it gets an assignee and a deadline you can track. Keep the vision, rocks and scorecards in your EOS software. Tallyfy is where the documented processes run.

The Process Component is one of six components in the EOS Model ↗[1], beside Vision, People, Data, Issues and Traction. It asks whether your core processes are “identified, documented, simplified, and followed by all.” Vision and Traction get quarterly planning sessions and retreats, and People and Data get hiring strategies and scorecard meetings, while processes can stay in people’s heads or sit as documents on a shared drive. The Issues Component suffers too, because it can’t work properly when processes aren’t actually followed.

Running documented processes in Tallyfy

Section titled “Running documented processes in Tallyfy”

Each process you’ve documented becomes a Tallyfy template. Its steps are written once, with instructions on each step, and your whole team can open it. When you launch it, the tasks go automatically to the people, groups or job titles set on each step, so everyone follows the same steps. Every task has an assignee and a deadline, so you can see who’s late.

If only one person knows how vendor payments get processed, that knowledge leaves when they do. Once those steps are in a template, whoever gets the task next sees the same instructions, and a new team member can follow them without someone sitting beside them. When a person leaves, change the assignee on their template steps and reassign their open tasks in running processes. Steps assigned to a job title need no change, because you pick who fills that role each time you launch.

The Tracker view shows every active process in one place, as a board or a table, and who’s doing what in each one. An Integrator can filter it to overdue processes to see where work is stuck. A Visionary who wants to know where a process stands can look it up there instead of asking for a status update. Everyone else sees their own tasks and due dates in the Tasks view, and Tallyfy can email each person a digest of tasks that are due soon or overdue.

Handing a closed deal to operations

Section titled “Handing a closed deal to operations”

A CRM can mark a deal “Closed Won” without tracking the micro-tasks operations has to finish between closing and delivery, and those are the tasks that get lost. A Tallyfy template can run this handoff. It might start with an implementation kickoff checklist that several departments work through, and a check of the customer’s data before anything is provisioned. Later steps can schedule the work and hold technical setup until its prerequisites are done. Credit approval can be a step of its own, assigned to finance.

If a step has required form fields, nobody can complete it until they’re filled in. Middleware such as Zapier, Make or Power Automate can launch the handoff process when the deal changes stage in your CRM. See CRM and ERP integration.

Tallyfy figures in EOS meetings, scorecards and EOS ONE

Section titled “Tallyfy figures in EOS meetings, scorecards and EOS ONE”

Before each Level 10 Meeting, open the Tracker view and filter to overdue processes, so your leadership team sees which processes are running and which are late.

Two Tallyfy numbers fit an EOS scorecard: how many processes complete on time, and their cycle times month after month. Put them beside the business results already on the scorecard so you can compare. The same on-time completion figures can go into your Organizational Checkup, and into quarterly planning in Traction Tools.

Strategic planning stays in EOS ONE. Set step deadlines in Tallyfy so each process finishes inside the 90-day rock it supports, and update project status in EOS ONE from actual task completion in Tallyfy.

You add these figures yourself, from a Tallyfy CSV export or Tallyfy Analytics. A CSV export of your processes gives you figures to add to your EOS ONE reports. For recurring reports, the Tallyfy Analytics add-on lets BI tools like Power BI read your Tallyfy data.

What an EOS Implementer can do with Tallyfy

Section titled “What an EOS Implementer can do with Tallyfy”

If you’re an EOS Implementer, import your clients’ existing process documents as templates, and the processes you help them document start running sooner. Their own team can keep changing those templates after your engagement ends. In coaching sessions, show them which tasks finished on time and which are overdue.

How to start

Section titled “How to start”
  1. Pick two or three processes that cause friction right now. Turn each one into a template, or import an existing Word or PDF document as a draft template. Use the same terms your EOS documents use.
  2. Launch a process each time that work starts, and show your team how to find and complete their tasks.
  3. At your next quarterly planning session, use last quarter’s on-time completion and cycle times to set process improvement goals. Find the steps where work waits longest, change them in the template, then compare cycle times before and after.
  4. Duplicate the improved template for other departments that run the same process.
  5. At annual planning, choose the next processes to move into Tallyfy.
Section titled “Related articles”

Introduction

Tallyfy helps you fix your processes first. Move your SOPs, flowcharts and checklists into…
Get in touch
About Tallyfy