Accounting for run-the-engine work (e.g. payroll) among an org-wide goals framework

I have a PMO-like role in my small organization. As we continue to evolve an org-wide goals and objectives framework for defining strategic work, and plan for ways to leverage Asana to track progress towards those goals, we are trying to take into account a certain tension that comes from having some work that directly relates to these goals and some work that doesn’t.

Big change initiatives are easy to map to org wide goals and objectives, and people feel good that they’re working on those things and can see clearly how their day to day work contributes to the bigger picture.

However, more BAU-type work–e.g. payroll, accounts payable–won’t map onto org wide goals and objectives. People who work predominately on this type of work may feel like their work isn’t valued or that their day to day feels disconnected from the broader mission of the organization.

I’m curious to learn how others have tackled this challenge: have you tried to build out team-level operational objectives or KPI’s that cover nearly all BAU work, AND tied that work to Asana? Or have you left that sort of work outside of any sort of framework (Asana or otherwise) and just managed the work connectivity part through other forms of recognition?

1 Like

Hi @Mark_Lee2 ,
I would definitely try to include the BAU work in the goal structure. As you say yourself - it is good for those teams to feel included and their work to be visible. After all, no other teams would be able to do their work if it wasn’t for those pillars of work structure!

I’m sure all teams have some type of targets they work towards regularly. Perhaps you can incorporate those into the goal structure? Maybe it is time to complete their work, or some other measurable value that can be captured through tasks? Connecting those to your goals would definitely contribute towards visibility and making sure nobody’s efforts get overlooked!

1 Like