Jeff Zigman Business Process Analysis/Optimization/Automation

You lose months and $ every time a wrong decision is made near the beginning of your startup, and every time decisions are made without a full picture of what needs to be built, or a clear technical direction of where you need to go. Most software startup founders go straight to hiring developers and never properly gather business requirements or create specifications before starting development. This should be Step 1 in any software if you want to turn out well, and to not drag on for months. If you don't gather business requirements properly, it's like building a house without asking how many bedrooms or bathrooms. How do you know what to put in the "blueprint" to build? If you don't create specifications properly, it's like not creating a blueprint before building a house. How could it possibly turn out right? Business Requirements are Step 1 and specifications depend on the business requirements. All subsequent steps depend on both of these steps. The less you do them properly, the more you will go in the wrong direction. See my LinkedIn video post here: https://www.linkedin.com/posts/jeff-zigman-17ab543_businessanalyst-software-activity-6660515085724774400-2uIU

I've learned how to find and hire capable developers, while filtering out the ones who can't get anything done. I've worked professionally in software for more than 13 years, and I've worked with more than 50 developers. I've also seen hiring processes that commonly used which make no sense when trying to find a quality developer. I've lead multiple software development teams and I've worked with some very skilled developers, and those that get so little done as the months pass that you want to pull your hair out in frustration. I have also developed a near-full-proof way of testing a developer's capabilities.