Results & Relationships

Become Better at what - 
Thinking about Minimum Viable Product, and Viable Skills longterm

Your calendar and priorites tell a tale of your future

if most of your day is meetings you most likley will become better at sitting in meetings.

Ask yourself why you didnt send a memo instead. Clearer and saves everyone involved alot of time.

If not - whats that about and whats the skill there'in you want to become better at?


From the outside it might look like you're taking a very long crashboarse into how to work with wague unclear people. 
Thats gimping your results.

or the opposite.
If you're programming for the same ecommerce platform again and again without no real intention.

Like Bruce lee said.
I fear not the one who have practiced a thousand kicks
I fear the one who have practiced ONE kick a thousand times.

but just doing what youre told as programmer is NOT putting yourself on the line in making better stuff so what IS that think you want to learn to be better at in your elite code-skills

in agile we talk alot about Minumum Viable Product
We dont focus our effort enough on the Viable part

Viable means its actually helping the client get to where they need to go, from where they are. Scrappy solutions are ok to start with but focus on the actual customer 
Not just that you moved something forward towards green.

Direct download: Become_better_at_what-the_viable_parts.mp3
Category:general -- posted at: 3:17pm GMT