Continuously Deploying Points of View
Applying continuous deployment thinking to ideas and perspectives: publishing thinking iteratively rather than waiting for the perfect article. The case for continuous intellectual deployment.
These are interesting times.
If you’re an agile practitioner (like me) you’re navigating a lot of uncertainty.
What’s the right language?
“Should I talk about Agile? Avoid it? Take a contrarian view of it?”
“Is Agility better than Agile? Worse?”
“Should I talk about SAFe? Scrum? or better to talk about Product?”
Agilists are struggling to stay relevant. And to fight harsh perspectives.
It’s a great time to develop (or polish) your point of view.
Developing ANYTHING in a field of uncertainty requires iteration. Transparency, Inspection, and Adaptation.
How can you do that for a point of view?
You can write point of view slices. Even that process will make it transparent, and enable you to inspect it.
You can also publish it. Get it in front of people. And inspect whether they engage with it.
The more slices you get out there, and the more frequently you do it, the faster you might work through point-of-view options and converge towards something that works.
Here’s the thing:
Daily Emails. Continuous Deployment for Ideas. Used for developing your point of view.
And testing it with yourself and your audience.
What are some ways you’re getting faster feedback on your ideas?
Practical thinking on turning AI pilots, adoption, and portfolio work into business impact - by finding the constraint, changing the work, and proving value as you go.
Yuval Yeret helps product and tech leaders move from agile theater to evidence-informed delivery. Work with Yuval →