The question often arises as to whether templates and processes are too restrictive, or even unattainable, because “every project/client is different”. Here are 5 reasons why I think exactly the opposite is true.
The question often arises as to whether templates and processes are too restrictive, or even unattainable, because “every project/client is different”. Here are 5 reasons why I think exactly the opposite is true.
Over the course of my career, I have had the opportunity to be part of the recruiting process for hiring Business Analysts for a few companies I’ve worked for. Most recently, I have spent the last 3-4 weeks up to my eyebrows trying to find senior BAs to join our quickly growing team. Having screened…
Don’t waste a single day of your knowledge transfer time! Here are some tips when you are the departing employee.
Weekly Wrap Up: Incident Tickets, Stepping Up, FAQs, Compliments, Kids & Clouds

Have you ever reviewed a printed version of a document and had to do a little work to figure out what you were looking at? Have you dropped a stack of papers and couldn’t figure out how they went back together? How do you know if you’re looking at the most current version of that document? All of these problems can be easily solved by using smart headers and footers.
There are various types of diagrams and techniques, some with more formal usage conventions than others. And there are some pretty slick tools that can help you simulate processes…but what if you don’t know how to use the formal techniques yet? What if you don’t have fancy tools?
You can still be very effective using two basic shapes and some arrows.

Not everyone gives thought to document naming conventions but this is one small area where you can help to bring clarity and ease of use to the many documents you produce on a project. By providing a consistent and easy-to-understand method of naming documents, it will make it much easier to organize information and find the exact document you are looking for.