# EoS Traction Tools App

**URL:** <https://community.fibery.io/t/eos-traction-tools-app/1617>\
**Category:** Fibery Showcase\
**Created:** [May 12, 2021, 6:04pm UTC](https://community.fibery.io/t/eos-traction-tools-app/1617 "2021-05-12T18:04:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rothnic](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/rothnic/32/1850_2.png) [@rothnic](https://community.fibery.io/u/rothnic)\
**Post date:** [May 12, 2021, 6:04pm UTC](https://community.fibery.io/t/eos-traction-tools-app/1617/1 "2021-05-12T18:04:34Z")

</div>

This isn’t yet sharing an app, but sharing an opportunity.

## Background:

- EOS = Entrepreneurial Operating System ([website](https://www.eosworldwide.com/))
- It is a business (consulting, software) built around the process defined in [this book](https://www.amazon.com/Traction-Get-Grip-Your-Business/dp/1936661837) with the goal of getting “Traction” for your business
- It is a mostly portfolio-level process for project management
- Our exec team uses traction.tools ([mytractiontools.com](https://www.mytractiontools.com/)), which you can see in all its glory in [this video](https://www.youtube.com/watch?v=rWlNdYgyuVE)

## Disclaimers:

- As a product management professional, I’m not endorsing this process
- My personal experience is that it overlaps with product development and has no clear connection to agile processes
- The tools seem to be mostly used by exec teams, but are intended to be used by the whole organization. However, since they are purpose built tools, they lack a lot of functionality people would expect. This means that we have some strategy-level data in one system (traction tools), and the rest in other systems (roadmapping tools, jira, etc)

## Opportunity

- Look at the process that is being supported and see if there are any missing capabilities that would enable building an app to support this process
- Build a shareable template so that people searching for Traction Tools, etc would find Fibery

## Research

- At first you might think that we should just setup an integration with Traction Tools
- I’ve found that Integromat has a [Traction Tools integration](https://www.integromat.com/en/integrations/traction-tools/), but is missing some key elements (Visual Traction Organizer (V/TO))
- I’ve also found that the data returned from the integration is as rich as it is in Traction Tools, which is not very
- This, along with the simplicity of the available purpose-built tools, is why I think it might be better suited to build an app that would just replace traction tools
- Rocks are essentially goals/projects with a due date, which is similar to Objectives in fibery’s Strategy app
- Measurables are similar to Key Results in the fibery app, but don’t have a current value. Instead, they serve as an ongoing definition for the metric, which is updated each week in the “Level 10 (L10)” meeting

### Types (via Traction Tools Integromat integration unless specified)

- Rock
  - Id
  - Name
  - Owner (object)
    - Id
    - Name
    - ImageUrl

  - DueDate (datetime)
  - Complete (bool)
  - Completion (single select [OnTrack/OffTrack])
  - CreateTime (datetime)
  - Archived (bool)
  - Permission (?)
  - Origins (?)
  - HasAudio (bool)

- Measurable
  - Id
  - Name
  - Owner (object)
  - Admin (object)
  - Target (integer)
  - AltTarget (integer?)
  - Direction (single select [GreaterThan, …])
  - IsDivider (bool)
  - IsReorderable (bool)
  - Cumulative (bool)
  - CumulativeRange (datetime)
  - Modifiers (string for units, ex. Dollar)
  - Ordering (?)
  - Disabled (?)
  - Generated (?)
  - IsFormula (bool)
  - Average (?)
  - ShowAverage (bool)
  - AverageRange (datetime)
  - Permission (?)
  - Origins (array ?)

- Headlines (used in meetings as a notable announcement)
  - tbd

- Issues (used to represent a problem to solve in a meeting)
  - tbd

- To-Dos (used for other individual tasks associated with meetings or people)
  - tbd

- Visual Traction Organizer (not exposed via Traction Tools)
  - tbd

## Challenges

#### Matching the Display

One of the key components in EOS is the “Visual Traction Organizer”, which is a visual representation of something like a Product Vision.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/0d37f85ab8909408abd1ca1123eaec3b5843fe8e.png)

There is no way in Fibery to build custom layouts of Types. For comparison, I was able to build a custom view in Coda where I started to build out an EOS document from the examples in the EOS book referenced previously. See below:

##### Example in EOS Book:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/b/b8dd20f31707ac70f0d3e21484a9c10257e3c869.png)

##### The Data:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/9d4cb9308e61f35a88a3f425cb56a33cc671556f.png)

##### The custom layout:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/4/4f6aab2aae94746412eba74bc5ffc28cae3212bb.png)