Section 2
Core Questions to Determine the Right Approach
The right model depends on how work actually happens
Because organizations operate in very different ways, the appropriate capitalization approach can vary significantly. A few key questions help determine which model will work best.
- The dynamics of the work itself. Some teams operate in highly fragmented environments where engineers move between many different tasks during the day. In these environments, broad quarterly heuristics can easily become inaccurate. Other teams spend most of a quarter working on one or two initiatives with relatively stable patterns, where a simple allocation may be sufficient.
- The structure of team collaboration. If teams typically work together on a small number of initiatives, team-level heuristics can often provide reasonable estimates. However, if individual engineers regularly work on many different initiatives for different stakeholders, individual-level tracking may become necessary.
- The organization's need for precise internal cost reporting. Some companies maintain internal chargeback models where departments invoice each other for work performed. This typically pushes toward more detailed tracking. Companies that only need high-level cost estimates for planning can adopt simpler approaches.
- Whether existing operational metrics correlate with time investment. Many engineering teams already track work through story points, story counts, pull requests, or ticket throughput. Determining whether such proxies reliably reflect time investment can dramatically simplify the capitalization process.
| Dimension | One End of the Spectrum | The Other End of the Spectrum | Implication |
|---|---|---|---|
| How dynamic and fragmented is the work? | Teams spend long stretches working on one or two initiatives with relatively stable patterns | Engineers move between many tasks during the day with maintenance, production support, and multiple concurrent initiatives | Stable environments can rely on higher-level allocation. Highly fragmented work often requires more granular tracking. |
| How team-oriented is the work? | Teams largely work together on the same initiatives with shared rituals and collaboration | Individual engineers frequently work across many initiatives and stakeholders independently | Team-level heuristics work well in collaborative environments. Highly individualized work often requires individual allocation. |
| How precise does internal cost reporting need to be? | The organization only needs approximate cost estimates for planning or oversight | The organization uses internal chargebacks or must invoice other departments for work performed | Higher precision requirements typically push toward more detailed tracking approaches. |
| Do existing operational metrics correlate with time investment? | Metrics such as story points, ticket counts, or pull requests closely correlate with time investment | Operational metrics do not reliably reflect engineering effort | Reliable proxies can dramatically simplify capitalization. Weak proxies often require more direct tracking. |