Haha! I’m seated here thinking, “Should I change this title from ‘Idea’ to ‘Rant’ instead?”. It would be very fitting seeing as a pattern seems to have emerged whereby I observe something and rant about it which inevitably leads to me penning my rant. The rant develops into an idea for a Product or a feature. Sometimes, if I’m lucky, the Company (or another) coincidentally makes those changes or builds the feature/product and Uchenna is a happy girl! That’s the end of my story.
As tradition dictates, Uchenna (yours truly) almost always has to turn these rants into a long-winded but, be honest, truly insightful 100-page article. What can I say, I can’t defy tradition, can I? ;)
I have observed that companies, especially ones with legacy systems, tend to have overwhelmingly long workflows from the customer to the Product Development teams. Many issues may arise from legacy workflows with minimal or outdated technologies integrated into these processes.
However, the biggest issue in a scenario where a digital product is involved is that highly useful user data is scattered across multiple channels within the workflows, and tasks to collect, collate and synchronise the different datasets are unnecessarily arduous. In some cases, you might even find that datasets overlap or analyses of the data might differ.