Log In | Become a Member | Contact Us


Market Intelligence for Printing and Publishing

Connect on Twitter | Facebook | LinkedIn

Featured:     Industrial Print Analysis     European Coverage     NEW PODCAST: Conversations on Print

Premium Commentary & Analysis

Set a Deadline for Print Software Transition

Retiring software solutions can be overwhelming. Continuing to pay maintenance on legacy software solutions is maddening. Start the process of transition by setting a realistic date – draw the line in the sand, rally your troops around what it takes to get from where you are today to throwing a retirement party for your legacy software.

By Jennifer Matt
Published: February 8, 2017

PREMIUM MEMBERSHIP CONTENT

This article is part of our premium member access. If this commentary & analysis is relevant to your business, please consider supporting us by becoming a member.

FOR FULL SITE ACCESS: LOGIN OR BECOME A MEMBER

 

Jennifer Matt is the managing editor of WhatTheyThink’s Print Software section as well as President of Web2Print Experts, Inc. a technology-independent print software consulting firm helping printers with web-to-print and print MIS solutions. You can reach her at jen@whattheythink.com.

 

Discussion

By Cory Sawatzki on Feb 08, 2017

I have been part to this process, and I love it. Not only that, but the people involved love it. Thanks for another great piece of insight Jennifer.

 

By Jennifer Matt on Feb 08, 2017

Cory,

Thanks for your comment. Its amazing how much people have to give when you create an environment where everyone has a "safe" and comfortable place to put their input. The post-it note is my favorite tool (doesn't require you to be a good writer, drawer, speaker, speller, or presenter). Just the ability to put your input down in a few words.

jen

 

By Brian Shipe on Feb 08, 2017

Love this Idea Jennifer. The Post-It Note method is also used in the Agile Software Development Model. While Capturing "User Stories" the author would document a simple sentence or two as an easy way to capture the Who, What, and Why of a requirement. Using that as the foundation for a Task or Feature, is a great way to "Eat the Elephant" of an MIS Replacement one bite at a time.

In your Experience, can this Cross-Functional Group be too big, or can you collect too much input at this step?

For example, using a Company Wide electronic survey to collect this input rather than meeting in a room.

 

By Cory Sawatzki on Feb 08, 2017

I think I have a picture of Jennifer going through this process at a customer. I was so tickled by it the first time I saw it, I could not stop smiling. Great stuff.

 

Post a Comment

To post a comment Log In or Become a Member, doing so is simple and free

 

Become a Member

Join the thousands of printing executives who are already part of the WhatTheyThink Community.

Copyright © 2017 WhatTheyThink. All Rights Reserved