One big mistake I see frequently is made when an organization thinks that "no code" means "no technical skills" required in order to build and deploy workflow-driven apps. The business sees an easy drag and drop, point and click interface and assume the whole project requires about as much skill as using Outlook. They assign their lowliest analyst, skimp on training, assign them complex projects with subtle behaviors, and are then surprised when the whole effort goes nowhere.
likes to say (and forgive me if I'm misconstruing) that building processes is just like writing code—I don't agree with that idea specifically, but his point is well taken. It doesn't matter how simple is the tool itself: complex problems demand a certain amount of skill on the part of the problem solver.