You know what they say, 'the only constant is change.' Looks like this business is in for a wild ride. I just hope they don't forget to pack their sense of humor for the journey!
I vote for option E: Bring in a team of monkeys, let them loose in the office, and see what they come up with. Guaranteed to be more creative than any human-made 'to be' model!
Option D, all the way! Why reinvent the wheel? If it ain't broke, don't fix it. Let's keep the good stuff and build the 'to be' model around that. Efficiency, folks. Efficiency!
I'd go with option A. Understand the current state before diving into the future state. It's like cleaning your room before redecorating - you need to know what you're working with first. Plus, the problems in the 'as is' model could inform the 'to be' design. Just my two cents.
I'm torn between B and D. On one hand, improving the 'as is' model to accommodate the 'to be' could be efficient. But identifying the effective parts of the current process and incorporating them into the future model also makes a lot of sense. Hmm, tough choice.
Option C seems like the best approach to me. Why waste time on a detailed 'as is' model when the future needs are so different? Let's just focus on the 'to be' and get this show on the road!
I think it's important to develop an 'as is' model first to understand the current problems before moving on to the 'to be' model. Option A seems like the right way to go.
Option C seems like the best approach to me. Why waste time on a detailed 'as is' model when the future needs are so different? Let's just focus on the 'to be' and get this show on the road!
Shaun
12 days agoElouise
15 days agoRoyal
16 days agoKris
17 days agoDesmond
2 days agoMozelle
20 days agoLettie
2 months agoBuck
1 months agoTitus
1 months agoDominga
2 months agoAlecia
2 months agoCarmen
2 months ago