In the previous sections, we discussed techniques that can help with making the tracing rollout a "zero touch" process, that is, without requiring any additional manual work by all the application teams.
Sadly, very often a completely hands-off approach is not feasible, otherwise we would have seen a much higher rate of tracing adoption in the industry. Therefore, since we need to spread the work across the organization, we need to address some organizational questions:
Where do we start?
Is it all-or-nothing or can we do an incremental rollout?
How do we get buy-in from the management and application developers?
Once again, I do not presume to have a rule book that guarantees success. I have, however, observed some common patterns from discussions with industry practitioners. The most common advice people give is this: start with the workflows that are most important to your business. For example, for a ridesharing app it is more important that the workflow for taking a ride is...