Knows everything about anything. But has no idea how to execute on what they know. This is why they are called a “Know it All” and not a “Do it All”. Big difference.
If development has yet to start, they are not Change Requests. They are requirements that were left out. They are a cause for concern because the delivery is changing before it can be built. They are a moment to pause and ask the customer what problem you are really trying to solve. They can be the start of a conversation to get back on track. But they should never be accepted verbatim because at this…
What’s the value of an anonymous up click on a skill someone might not really know that you have when instead you can post a video of what you do? Or better yet have a customer create that video, staring at their phone saying how you helped them solve a problem. The Endorsements model is a great idea in theory but fraught with inconsistency as you can very easily endorse everyone on the page without…
It’s still there, you simply turned off the tap. You let the workload get you down. You let everyone’s else’s demands supercede your own. You tried to make it happen, it didn’t and you became frustrated so you stopped. If you want to get the creativity back, stop thinking of it as some magical genie in a bottle and start seeing it as the labour of work and love that you need to put in…
It’s not easy to do when around you everyone wants something. They want what everyone else is doing and achieving. They want the overnight success that others are achieving. They want to reach their goals faster and sooner than the last guy. But they aren’t ready for it because they haven’t quantified the need. They haven’t figured out what they need to do before they can start wanting something. These are the hardest conversations with…