![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Systems Failure
Mar. 29th, 2007 12:00 pmThere are some fantastic systems out there. Things that help you manage people, products, files, whatever. I've been introduced to quite a few, since I entered the workforce, and I've even created a few myself. Workflows, calendars, version control, all of these things are great for making sure that everyone's on the same page. Systems keep things from being forgotten, help you fix problems, help you undo or prevent changes that may not have been such a great idea to begin with.
I do have a tendency to fly by the seat of my pants, as a general way of leading my life, sure. But the fact is, I LOVE having a system for processes that I do repeatedly and frequently, especially when it comes to my work. I have a short attention span, and ideas or thoughts tend to fly in and out of my brain at their own whim, so having a set way of doing things helps me get back to a thought that might've escaped from my conscious thought process before I could act on it.
Having a system for processes when working with other people is great, too, because hey, maybe *they* have ADD-like tendencies, or are generally forgetful, or just have a different way of doing things. Maybe they're further along in the process than you are. Whatever it is, you have a way to get yourself on the same page as the other person, and you can actually move forward and avoid confusion and redundancy.
When does the system fail, though? When people agree to using those systems, be it explicitly or implicitly, and then DON'T USE THEM.
Using a calendar to track appointments doesn't work, if the entire group doesn't log their appointments. Using a process flow doesn't work, if the people using it regulary skip steps in the process. Version control doesn't work for a project, if any individual who is working on said project doesn't check in their changes.
That? That is today's point of frustration.
GRR ARR STOMPY
I do have a tendency to fly by the seat of my pants, as a general way of leading my life, sure. But the fact is, I LOVE having a system for processes that I do repeatedly and frequently, especially when it comes to my work. I have a short attention span, and ideas or thoughts tend to fly in and out of my brain at their own whim, so having a set way of doing things helps me get back to a thought that might've escaped from my conscious thought process before I could act on it.
Having a system for processes when working with other people is great, too, because hey, maybe *they* have ADD-like tendencies, or are generally forgetful, or just have a different way of doing things. Maybe they're further along in the process than you are. Whatever it is, you have a way to get yourself on the same page as the other person, and you can actually move forward and avoid confusion and redundancy.
When does the system fail, though? When people agree to using those systems, be it explicitly or implicitly, and then DON'T USE THEM.
Using a calendar to track appointments doesn't work, if the entire group doesn't log their appointments. Using a process flow doesn't work, if the people using it regulary skip steps in the process. Version control doesn't work for a project, if any individual who is working on said project doesn't check in their changes.
That? That is today's point of frustration.
GRR ARR STOMPY
