Re: resistance to new technologies/workflows
New workflows, new technologies, anything new can be as impressive as your new car. Where the difference can be is the road. That car can drive 145 mph on the highway, but if you need to take a quick exit, find yourself on a mountian dirt road, what's happened?
I am always looking for a better way. When we did a type change with the old Scitex/Brisque, I could have new plates within a half hour once the page was RIPed. This was 5 years ago. Now, I have to RIP the page and RIP the Imposition. Someone said since I'm on .eps workflow with Rampage, I don't have to do that. I haven't figure it out yet, but I'm still searching for answers.
We do have monkeys here. They resist any change. We can't new team players, so I'm stuck. "Don't open Quark 6 with Quark 7 (Rolling eyes.)." It's still done every freakin day. How can I change this. Go find another job!
The best way to fight that resistance is to understand it yourself, then pose questions in a different manner. If you don't know prepress from the conventional way, you may be missing something in your quest to change the workflow.
It's like our owner never liked prepress because he doesn't understand it, nor does he care. His son is RIPping pdfs. So, we get a real job in, and now he's lost. The sad part, we've trained this boy for 8 weeks. Sure, he's learning, but now the owner believes it is easy and we're just old, dumb guys that he's paying too much money for a job monkeys can do.
-It would be interesting to know what you've presented to these guys.
Our supervisor is a graphic designer coming from a conventional art background. He knows very little about printing. What is the problem here? Talk about aloof!! If I ask a question about a job, he tells me how to do it. "No, do I delete the word or delete the background?" He proceed to show me again how to change color. LOL
Everything is relative. If this was a smaller company using a GTO or AB Dick, I'm sure he could fit in. Understanding die cutting, perfect binding to saddle stitch pagination has resulted in hair loss. Literally.
We had a problem with trapping on one file. "Why are you trapping?" So guess what? We don't trap anything. I'm not kidding!
I use Rampage/Preps. You've gotten my curiosity about workflow and change. Is it resistance or caution? I explained my reasoning and that was taken into consideration.
We had two types of workflows proposed with 5 Mac operators. I resisted #2 because we were too small of an operation. Each is would be crosstrained but bottle-necks and inefficiency would occur as time went on because of the reduced experience in the cross training.
1. Each operator will prefight, work/alter, RIP, proof and Imposition.
2. Each of operation will be separated an only one operator will be responsible for performing the operation.
I'm told I'm resisting change because I won't use CS3 completely to work on all CS and CS2 files. I'm pretty sure this will be the camel's back that breaks the straw.
Frank