If you can’t get them to trust each other if you can’t get them to find that common ground. How can you expect them to build an app? How can you expect them to build a system? How can they execute on your system? What will they do when things go wrong? Find the common ground, wherever it is, and start there.
When you start building code, insurmountable amounts of code that you had not planned on writing at the onset, to work with the platform. It’s time to move on. You tried, the fit isn’t there, move on.
The question your team will ask over and over again if they don’t understand your vision, or if they forget, or if they get lost along the way. It can be frustrating for a leader to hear that after they have poured so much into making it happen, into making it worthwhile, into making it something only to be hit a dismissive – “Why are we doing this?”. Make sure they always know it, make…
Your membership has privileges. If you’ve been a member somewhere for a few years, that should buy you some goodwill – a thank you, some forgiveness if something goes wrong, a check-in, etc. That’s the whole point of membership – being part of something that people care about. We’ve devolved membership to be “Sorry to see you go.” as opposed to “What did we miss?”. If you’re building a program that requires membership, start first…
On a recent trip overseas, on a tour bus, I saw this gathering of our future Robot Overlord Masters gathering – perhaps by chance, perhaps by circumstance, perhaps on purpose. But yes, everyone needs a break to get some shade once in awhile.