In today's business world, having a cohesive technology strategy and high-performance business operating software isn't just a luxury, it's an absolute requirement. However, software by itself is not a solution; it's a piece of the overall puzzle. Software is designed to speed up the performance of tasks, but in the absence of proper processes and workflows, that can mean speeding up making errors instead of achieving proper outcomes.
When I work with clients on implementing business operating software, I always start with the introduction of core standard operating procedures and standard role definitions that align with the steps of each process. This ensures that we are automating the proper steps in the proper order so that proper outcomes are the result:
This approach provides for a consistent, conscious stream of data that can be accurately compared and evaluated when making management decisions about the work and the business overall.
Processes outlining which roles are responsible for providing, reviewing, approving and/or adjusting inputs and outputs are essential to ensuring data consistency and the system outputs. The estimating process might involve more than one person, depending on the size or scope of the job:
This process is typically executed partly in the system and alongside it.
When it comes to the reporting function of the software, it is important to ensure there is enough flexibility to report key metrics to your business approach, and that they align with the role and process definition. Reporting all kinds of data can feel important, but if that data cannot be understood by the people in your business in a way that can inform their decisions and actions, it is worthless.
I suggest no more than five key performance indicator metrics per role in your business, to be determined through a collective review and discussion with the entire team. Each role's KPIs should be tied to outcomes in the business's KPIs.
Regardless of the software you choose, don't overlook the importance of standard defined roles, processes, and KPIs per role before implementation. This approach will set you and your team up for success with your new system and ensure you are not simply making mistakes faster!
Crucial operating software elements