Storyboarding Futureproofed Workflows

This entry is part 14 of 18 in the series Interview Tom Marine Gets Right Upfront

MM: Brilliant! So then, that gave you an optimized workflow that you could visually depict—probably using pretty standard workflow diagrams. Right?

TM: Yes. Sometimes there would be a written step. Sometimes it would be a screenshot with the new data. Sometimes it would be a screenshot of a directory.

MM: So these are basically the artifacts that went into the user manuals.

TM: Correct. That’s exactly what they were. Yes.

MM: So now in the course of then developing this optimized workflow—creating it one screenshot at a time.

TM: Yes.

MM: In the course of developing these screenshots, you had the operator—the intended operator—come in and interact with you and ultimately say, “Yes. That’s what I want my screen to look like.”

TM: Partly. Remember that we really hadn’t chosen the vendor, yet at that point. There were basically mockups that were just done in Excel that showed a basic idea of what it would look like from a data standpoint. But not what it would look like visually in the application.

MM: Perfect! So you developed the wire frame or the exposed data model for that particular screen or activity?

TM: Yes.

MM: Then, how long did it take you to develop that idealized workflow model?

TM: I was trying to think about that—how we broke that down. It was nine months for the total. My guess is that it was like six months for the current workflow and three months for the optimized.

Posted in:

Leave a Reply

Your email address will not be published. Required fields are marked *