Why 'Working Smarter' is so much smarter.

Working smarter, not harder is a term used regularly to make sure we make the best use of the limited resources we have. Not surprising that more organisations are looking at how to work smarter and ON-Brand clients are achieving some impressive results.

Recently an ON-Brand client completed their working smarter conversations and we couldn’t be more delighted to see some of the feedback that came from them. Quite often working smarter is about questioning why we do some of the things we do on a regular basis. Does it add value? Does anyone even use the output?

Getting teams together to have focused conversations about these things can deliver some impressive results as you’ll see from this feedback.

"(Our) team has used the principles in the Work Smarter not Harder module to bring upon some changes within our area.

XYZ, has run two workshops  for the ABC teams, and I was fortunate to attend both.  The workshops where a great success and the teams identified tasks that we really didn't know why we still did them, but continued to completed because we always have, in one instance this saved a staff member 2 hours a day.  We also identified changes to processes which we could action within the team without the support of other teams/resources.  A number of these changes have already been actioned and we can see the benefit.

I strongly recommend that you implement the Work Smarter not Harder module with your team."

2 hours a day! That's 10 hours a week or 500 hours a year. Now that is working smarter!

Another team member shared this...

"This week a couple of members of my team (Team A) had a meeting with team members from another part of the organisation (Team B) regarding migrating data from a standalone database into a corporate database.  Within 10 minutes we had determined that:

• the newest member from Team B was entering data into the database with no understanding as to why it was required.  They were doing this just because it they were told to by a previous staff member.
• other team members from Team B were not using the database – systems have evolved and the information can now be easily sourced through other corporate systems
• we all agreed that the process of entering data into the standalone database was no longer required and we also did not need to migrate the data to another database

We estimate that by making this decision we have saved approx. 200 hours of work for the data migration, not including the time-saving for the data entry that is no longer required!

Working Smarter by communicating across teams and simply asking questions."

Is it time your people started working smarter?

See more on the Working Smarter, Not Harder theme here.