Many video games are based on similar engines and formulas. They know what works and they follow that plan, new games come along because the engine is proven and they re-use it to save money. The formula stays the same with little to no improvement, costs decrease, and the need to do “well” drops because development time was saved and we can do “meh”. Or you can stay in a hole for a while, or…
Someone makes a cool video and everyone jumps on. It becomes a trend and everyone starts to do it because they get views – the trend becomes bigger but then becomes stale as innovation drops. Now it’s just someone else doing the same thing they’ve seen a thousand (or more times). No one wants to do the same thing over and over again in life, but it exists for views (the exact opposite of why…
I’ve been on a project the last few months where I’ve had to do much of my own QA. I’ve had to write unit tests, write test plans, and test cases. I’ve had to debug assertions of what should and shouldn’t be. Turns out I’m not as great at QA (or diligent) as I thought I was. Worst yet, turns out there are a slew of errors in my code. So apologies to all of…
A plan is only as good as it’s execution. Otherwise, it’s an elaboration of an idea. And we have plenty of those.
We coach for wins, not for growth. Growth happens behind the scenes, no one sees it unless they look deep beneath the covers. But it’s always there. So what would happen if we coached for growth instead, letting the wins happen when they happen, and see where we get from there? What would be the harm? What could go wrong? Just growth.