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.
Treat your point of view like something you develop
These are interesting times. If you are an agile practitioner like me, you are navigating a lot of uncertainty. What is the right language? Should you talk about Agile, avoid it, or take a contrarian view? Is agility better than Agile? Should you talk about SAFe, Scrum, product, or something else?
Agilists are struggling to stay relevant and to respond to harsh perspectives. That makes this a good time to develop or polish your point of view.
Developing anything in uncertainty requires iteration, transparency, inspection, and adaptation. A point of view is no different. You can write slices of your thinking, publish them, get them in front of people, and inspect whether they engage.
The more slices you get out there, and the more frequently you do it, the faster you can work through options and converge on something that works. Daily emails can become continuous deployment for ideas: a way to develop your point of view and test it with yourself and your audience.
What are some ways you are 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 →