If you hire people just because they can do a job, they’ll work for your money. But if you hire people who believe what you believe, they’ll work for you with blood and sweat and tears.
Customers and product owners should not use the existence of emergent requirements as an excuse for shoddy thinking. Development teams have the right to expect them to make reasonable efforts at knowing what they will eventually want. But, just as product owners and customers cannot possibly know everything in advance, development teams need to stop expecting them to.
Simply ask people to walk you through their thinking. Why do you think that? Walk me through your logic.
Over the years, I’ve found that simply asking why and listening to the quality of the response is the best [nonsense] filter. If answers come back in cliches and generalizations, that’s an indication that more thinking is needed.
Sometimes when you think up an idea you immediately picture a vision of what the final product will look like - there’s going to be a wall, chat, portfolios, and more.
This can sometimes paralyze you from starting because the task seems so daunting, you begin to think that you’ll need to hire more people or raise funding to get this done.
Instead, my advice is to start. Don’t wait for everything to be perfectly figured out. If you start, you’re already 90 percent ahead of the game and you’d be surprised how far you can get
I believe the greatest businesses in the world are lead by a sense of mission and purpose.