Follow Us:

Call Now! + (317) 852-5163

I Don’t Know How To Do That!

Have you ever been frustrated because you were asked to do something but none of your co-workers knew how to do it? Not even your boss? Or “the way we have always done it” makes no sense and no one can really explain why it’s done that way? I have been in that situation. I look for documented processes on how to do it, but they can’t be found; or they are so old that the tools and recommended process is dated back to when the company started.


Every organization needs and generally wants documented processes, but it is hard to find the time to get them written, vetted and then finally stored. Who has time to write down how your organization is supposed to do all of the tasks and jobs within? Does it matter? Is it necessary?


Process Development is important work for a company to:


  • Have consistency
  • Help train new staff
  • Set a standard that brands your company
  • Meet industry standards and regulations


Every department has its own core purpose and some standardization but sometimes sharing that can be a challenge. Until you actually start writing them down, you probably haven’t questioned if it is the most efficient way or if it meets new standards. Does the way you do it today make sense or is there an easier, smarter way?


It’s always a good idea for the team to agree on what processes work the best and which processes cause the team to falter or lack clarity. Have you taken the time to determine what works and what doesn’t? That is a great place to start. It may seem taxing but if you start by just jotting down a quick note when something works really well or when something causes an issue then you can go back and do the autopsy later; dig into the details and figure out where improvement can be made.


Additionally, once you are able to create your process documents, it is so much easier to train a new person. Once a person reads through the processes, sits with one of the experts on your team and then re-reads the documents, they should be pretty-well versed in the task. Or at least be able to ask good intelligent questions. Likewise, this is also a great way to vet the documentation, by having a new person test them. If it is not clear, then you will know by their reaction and ability and you can make updates. It is a work in process, no doubt, but much better than the inconsistency and guessing that can occur when no one really knows how to tackle a task.





Contact a CoreTech Expert Today!