The Impossible Project: A Corporate Staring Contest
When Marketing declared the need for a new product, the response from IT was anything but enthusiastic. Developers estimated a six-month timeline to implement the necessary changes, while Marketing insisted they only had two months before the competition would beat them to market. The tension in the room was palpable, with collective sighs and eye-rolls replacing any productive dialogue.
What followed felt more like a corporate standoff than a project kickoff. Both sides were dug in, neither willing to budge on their timeline. It was clear this wasn’t just a business challenge—it was a political minefield. That’s when they decided to call in outside help.
Bringing in the Consultant: Hope or Final Nail?
That’s when they brought me in—the external business analysis consultant experienced in dealing with “political” projects. I was armed with my trusty laptop, a love of diagrams, an experienced support team, and just enough caffeine-fueled optimism to believe we might crack this nut.
The IT manager greeted us with the warmest of welcomes: “We’re hoping this workshop proves to the business that the project is undoable. We don’t have the resources to pull it off.” Nothing like a little pre-workshop pep talk, right?
A Clash of Determination: Business vs. IT
On the business side stood Jim, the product manager, a man determined to defy the odds. Jim had invited 20 of his brightest and best people from all over the world to the workshop to ensure success. He introduced himself to us and the IT folks with a proclamation that could curdle coffee: “Well, you IT folks say this project is undoable. You’ve brought in this cracker-jack consultant to help me understand why. Now, I’ve never been to one of these ‘JAD sessions,’ but if I’m not convinced by the end of today that this process will succeed, I’m taking my folks to a different meeting where we can show y’all how it’s done in Texas.”
Not that I was nervous—just mildly terrified. But hey, what’s life without a little pressure? I just needed a little more caffeine.
The Turning Point: Finding Common Ground
Preparation was key. I had asked all participants to email their lists of problems the product needed to solve, along with any known IT infrastructure issues. During the workshop, we debated and refined these lists until both IT and Marketing agreed on a shared understanding of the challenges ahead—a rare and valuable consensus.
This alignment didn’t come easily, requiring two hours of intense discussion and occasional frustration. But by the end, we had reached a critical milestone: both sides were willing to move forward without labeling the project as “undoable.” It was the first glimmer of hope for a seemingly impossible task.
The Power of Diagrams: Building a Massive Data Flow Map
Next, I guided the group to create a massive Data Flow Diagram (DFD) on the walls of the conference room. Armed with sticky notes, markers, and a shared sense of purpose, we worked together to map out the relevant business processes, data flows, and data stores. Over the next couple of hours, the 30-foot-long diagram took shape, stretching across the room like a mural of collective effort.
This wasn’t just a technical exercise—it was a turning point for the team. The act of building the diagram together fostered collaboration and mutual understanding. What had started as a room divided now felt like a group united by a shared goal.
The Game-Changing Technique: Problem Analysis DFD Overlay
The pièce de résistance? A technique I called “Problem Analysis DFD Overlay.” Armed with their lists of problems (each with a unique identifier), the participants wandered the room, scribbling problem numbers on the diagram wherever they felt the pain-points lay. It was like a corporate Easter egg hunt, except the eggs were existential crises.
By the end of the day, the group was surrounded by the hand-drawn DFD replete with associated problem numbers. That was as far as we could make it on day 1.
Jim’s Verdict: A New Believer in Visualization
Jim stood up for the ultimate verdict. “I said this morning I’d never been to one of these ‘JAD things.’ Now, I’ve never understood our business process and problems better than I do right now. I can see why IT has such a challenge, but that doesn’t change the fact that we need a solution. I am convinced that if there’s a solution, this approach has the best shot at finding it quickly. Let’s get it done.”
I floated a couple inches off the floor for a few seconds before putting my heart back inside my chest where it belonged, then I introduced the agenda for days two and three.
A Grim Reality: The Six-Month Timeline Stands
We spent those days poring over the diagram, brainstorming potential fixes for every pain point. Hundreds of requirements later, a grim truth emerged: IT’s estimate was accurate. Updating all the applications would take months, not weeks. Over 60% of the problems clustered around a single early-stage process that was so problematic it could have starred in its own soap opera. IT clarified that this step had been a legacy thorn in their sides for years. They were afraid to touch it for fear of unforeseen consequences – typical of the interdependence between newer software applications and legacy programs.
That’s when magic happened.
The “Aha!” Moment: Bypassing the Bottleneck
Sharon, one of the business analysts, had been pacing the room like a detective on the brink of cracking a case. Finally, she pointed at the diagram and said, “What if we just bypassed this mess entirely?” She sketched out a new data flow that skipped the troublesome process and reentered the system further downstream. It wasn’t perfect—it left a ton of tedious cleanup work—but it was feasible.
This sparked lively debates, tweaks, and light bickering that are the hallmarks of progress. By the end of the workshop, the group fully embraced Sharon’s idea as amended. In just two weeks, IT implemented Sharon’s solution, and the product launched a month ahead of Marketing’s most optimistic expectations. The success was unprecedented, turning a seemingly doomed project into a market triumph. The collaborative effort had not only solved the technical challenge but also strengthened trust between IT and Marketing.
Jim, the product manager, summed it up best: “From now on, I’m never approaching IT with a change request until I’ve got a diagram like this and a solution in hand.” His words reflected the transformative power of visualization in solving complex business problems.
The Moral of the Story: Visualize for Clarity and Collaboration
Visualization proved to be the key to unlocking collaboration and innovation. By drawing out the problems, the team transformed chaos into clarity, making the impossible not only achievable but successful. This approach turned skeptics into believers and conflict into cooperation.
The takeaway is simple: when faced with daunting challenges, don’t just discuss problems—visualize them. And always keep an eye out for your team’s “Sharon.” She might just be pacing the room, ready to save the day.