Rockley ch 11
Disclaimer: Please do not take away from students who do not comment on this blog because it was supposed to be posted in early April.
Rockley Chapter 11: Designing Workflow.
Rockley describes what workflow charts are, what content they hold, and the pros for utilizing them in tandem with the unified content strategy.
A workflow chart is basically a flowchart with the various aspects (role, responsibility, and process) of a project planned out. Workflow charts can be flowcharts or swimlane charts. I find the swimlane chart the easiest to follow because it is like looking at a table, find your lane and follow it along to see what tasks are yours to complete.
Workflow charts work well into the unified content strategy because it is an easy way for every player to get on the same page with what tasks need to be done and in what order.
Rockley Chapter 11: Designing Workflow.
Rockley describes what workflow charts are, what content they hold, and the pros for utilizing them in tandem with the unified content strategy.
A workflow chart is basically a flowchart with the various aspects (role, responsibility, and process) of a project planned out. Workflow charts can be flowcharts or swimlane charts. I find the swimlane chart the easiest to follow because it is like looking at a table, find your lane and follow it along to see what tasks are yours to complete.
Workflow charts work well into the unified content strategy because it is an easy way for every player to get on the same page with what tasks need to be done and in what order.
posted by Matt Bynum | 8:52 AM
7 Comments:
Workflow systems are now integrated with major vendor document and content management systems. Workflow systems become increasingly more important as the size of an organization grows. Complex workflows can now be designed and work processes implemented due to the power of this type of software application.
I think the work flow chart is very important in any aspect. If for some reason one of the team members working on the project becomes wrapped up in something else or has to step away from the project then a different team member may be able step in and be proficient by utilizing the flow chart. I think it also creates organization. It lets everyone know when something needs to be done and in what order to do it. Definitely important to unified content management.
As Carl and Erik have both said, the workflow chart can be a very important tool in an organization. Erik’s example of someone who needs to be replaced is a good one. Sometimes the work environment can be very fluid—almost a little too much sometimes—so workflow charts can be a good way to track where a given project is going. This appeals to my inner control freak because I have to know what’s going on at all times! Where are we? What’s next? What’s coming down the line? I’m a little obsessive about stuff like that, so I think a workflow chart could help me curb those tendencies a bit.
Workflow exists regardless of whether we have a chart or visual to show us how it should work. Even without any guidance or workflow charts, business would carry on, tasks would get done, people would work their roles. But (and this is a big 'but') without a designed workflow system, people would get lost, argue about what they're responsible for, lose track of time, or do work that someone else is already doing.
I think it's important to look at this chapter as a method of streamlining a process that already exists. That, through a little preparatory work, you can make your workplace run more smoothly and efficiently than before.
I imagine what my job would be like if we didn't have pre-designed workflow. I work in a computerized kitchen, where orders are separated by roles. Food that is done by the fry cook only show up on the fry cook's screen, and when the food is done, the fry cook selects it as 'done' on the computer screen. When a whole table's order is done, the expediter sends it out to the table. This whole system helps the kitchen achieve very short ticket times, improves food quality (because it doesn't sit in the hot window waiting to be taken to the table), and keeps the kitchen from arguing about who should do which orders. Without our computer system, I think the kitchen would be in chaos.
I also posted chapter 11, so I'm not going to make any additional comments...but I did enjoy reading others'.
Workflow charts--in my opinion--are somewhat of an exercise in futility. I think this is one of those things that might be a better thing in theory than it is in practice.
I'm sure that, when done right---and as long as everyone does their part--a workflow chart can be a goood thing. Eveyone should know their function, although I suppose in complex projects the chart might be necessary.
I think these charts can make everything in a project run much smoother than without. it gives you an idea of what people have responsibility for as well as where they may be at on the project. It can give individual workers an idea of who to talk to if they have questions about something they are doing, or someone to give a heads up to in regards to your responsibilities. And it obviously makes a point to dictate a job to everyone and make sure everything that needs to be done will get done and not done twice or three times.
Post a Comment
<< Home