The people who run it or the IT department. No question, right? That’s why failing to communicate business requirements is never an IT issue. It’s a business issue.
We aren’t running IT projects. We’re running business projects that happen to be enabled by technology. And the people who own the process being automated are the ones who know what it needs.
Unfortunately, those people have trouble sharing that knowledge, and the IT team has trouble asking for it. The good news is there’s an easy fix and we can show you.
Sharing a ton of information and hoping you retain some of it isn’t a good way to develop skills or accelerate performance—and we’re after both.
We’ll point out the traps, show you the secrets, and give you the tools to get around the biggest source of IT project failures, but you have to learn how to use them. You’ll never master those skills by listening to us talk. You’ll only become a master by doing.
Our program develops mastery by utilizing a three-phase approach from Cognitive Psychology and Neuroscience that’s three times more effective than sharing information alone.
Phase One introduces the ideas. Phase Two establishes disciplined practice. Phase Three provides individual coaching to correct and refine the areas where each student needs help.
Scroll down to learn more about all three.
This is our foundation. It has four parts. Part one explains the frequency, costs and cause of the IT project failures we address. Part two unpacks the neurological factors behind that cause. Part three explains where those factors most often present themselves. Part four provides an overview of our solution.
The course is designed for executives, IT project leaders, and sponsors; business, process owners, and SME’s; heads of IT, tech team leads, external vendors and consultants; program or project managers and analysts. The course is for anyone interested in improving their ability to define and execute business strategies.
Two instructors for all live, remote sessions to provide depth, perspective and greater attention to each participant.
$1,495 per person.
Following the introduction, we offer this deep dive workshop for participants to get hands-on experience applying the Process Mining Roadmap (PMR) either to their project or our real-life simulation. The class is divided into a business and tech team. Each side is briefed with information and personas. On day one the tech team uses the PMR to extract as much information as possible form the business. On day two, the roles are reversed. New information is provided, and the exercise continues. The workshop ends with a review of key events, identification of lessons learned and best practices.
The workshop is designed for those taking a leadership or active role in IT projects: program or project managers and analysts; heads of IT, tech team leads, external vendors and consultants; business or process owners, and SME’s.
One instructor for both days of the workshop. All efforts will be made to ensure the instructor is one from the introductory course.
It’s time to apply what you’ve learned to your own projects. The frequency and duration of coaching is determined by the size of your project and needs. Our intent is to teach you how to fish—not to fish for you—but we will jump in if necessary to help you tackle major challenges. If the time required exceeds our availability, we can suggest qualified partners to augment your team.
Coaching is suggested for those taking a central role in any IT project: IT execs and tech team leads; project managers and analysts; SMEs and process owners. Coaching is required for those wanting to get certified to train and mentor others.
No less than one coach for every five participants. Coaches will be an instructor from the workshop.
TBD based upon
It’s the simple stuff that will kill you, but you’ve got to know what to look for. Here’s a few examples of how companies have used our Roadmap.
6 hours of work to clarify requirements was all it took to fix a sales pipeline tracking issue that had wasted 7 months and $120,000 trying to do the wrong things.
Spending just 50 hours to define requirements saved a critical data warehouse project that had wasted $2 Million and 18 months without delivering any results.
They got creative with the Roadmap and spent 1 month to reverse engineer a supplier’s true costs. That resulted in a savings of $5.4 Million on the renewal of a 3-year contract.
A little knowledge goes a very long way.