Trend Radar Interactive App
This modern web app provides you with an interactive trend radar. It is used to visualise and manage potential threats and opportunities across Political, Economic, Social and Technological dimensions. These strategic points are displayed in a concentric circle diagram.
- The outer ring represents trends with the lowest likelihood of occurrence, whereas the inner rings represent trends with increasing likelihood.
- The size of a point represents its potential impact, with larger points indicating a higher impact.
- The colour of a point indicates the preparedness level, ranging from red (low preparedness) to green (high preparedness).
Related Content
Building a culture of innovation in your business with GitHub
Consider the typical software development practices in an organization. Projects are commonly closed, and causes friction across engineering teams. But open source communities work asynchronously, openly, remotely and at global-scale. What if our internal teams could reuse those same practices?
Rapid Prototyping as a way to validate your idea
Rapid prototyping is more than quick coding — it is a structured discipline for learning fast and making smarter product investment decisions. In this episode, Chris is joined by Andrew Greenstein, CEO of SF AppWorks and host of "The Next Great Thing" podcast, to explore three distinct types of rapid prototyping: design sprints, iterative feature development, and platform proof-of-concepts. The conversation draws on Kent Beck's product development triathlon (explore, expand, extract), Saras Saraswathy's effectuation theory, and a West Elm innovation case study — where rapid prototyping an AI image-matching feature and a chatbot delivered measurable revenue gains.
Code is Read
What separates code that teams maintain with confidence from code that becomes an unmaintainable burden? Chris is joined by Daniel Schreifler — developer, consultant, and author of "10 Days to Become a Better Developer" — to explore why readability is the most foundational software quality. From cognitive load and the early-exit pattern to domain-driven naming, inner sourcing, and TDD, this conversation reframes how we should think about writing code: not for the compiler, but for the next human who needs to change it.