Bill Gates famously takes "Think Weeks" to step back from the daily grind and reflect on big-picture ideas - like the potential of the internet, which reshaped Microsoft's future. While most of us can't escape to a cabin for a week, we can spark similar breakthroughs by challenging ourselves with constraint-driven exercises (like the one we already wrote about here).
By imagining your team operating under extreme limitations, you uncover creative solutions, future-proof strategies, and fresh ways to tackle challenges. Below are ten scenarios designed to push your thinking and help you prepare for whatever comes next.
#1 - A World Without Deployments
You are no longer allowed to deploy new code or features for six months.
How would you focus your team's efforts on optimizing and maintaining existing systems? What processes would you improve to ensure the system remains robust and efficient?
#2 - A World Where All Code Must Be Written by AI
Your team is only allowed to use AI tools (e.g., Copilot, ChatGPT, etc.) to write code.
How would you define workflows and review processes to ensure quality? What skills would your team need to become experts at prompt engineering and validation?
#3 - A World Without Backend Systems
You're only allowed to use third-party services (e.g., SaaS platforms, APIs, services provided by AWS, Azure, or Google Cloud) for all backend functionality.
How would you select, integrate, and manage external services? What changes would you make to the frontend to support this architecture? How would you test new functionality?
#4 - A World Where Downtime Costs $1,000/Second
Every second of downtime comes with a steep financial penalty.
How would you prioritize reliability and uptime in your development practices? What monitoring and alerting tools would you implement to prevent and respond to issues instantly?
#5 - A World Where All Projects Must Be Delivered in Two Weeks
No matter the scope, all projects must be completed in two weeks or less.
How would you break down complex features into incremental deliverables? What changes would you make to your team's development methodology (e.g., sprints, Kanban)?
#6 - A World Where Security Is the Sole Priority
Your only KPI is security, and your team is judged on how airtight your systems are.
How would you conduct audits and prioritize vulnerabilities? What trade-offs would you make between usability, performance, and security?
#7 - A World Without Engineers
You're no longer allowed to have any technical employees, but you still need to maintain and grow your systems.
How would you transition to no-code/low-code platforms or outsource technical needs? How would you restructure the organization to manage and oversee external solutions?
#8 - A World Where Every System Must Be Replaced Annually
Assume all technical infrastructure has a maximum lifespan of one year and must be completely rebuilt.
How would you create modular, reusable components to speed up rebuilds? What tools or processes would you adopt to make migrations seamless?
#9 - A World Without Version Control
Your team is not allowed to use version control systems like Git.
How would you ensure collaboration, quality assurance, and rollback capabilities? What tools or workflows could you introduce to manage codebases effectively?
#10 - A World Where You Must 10X Technical Output Without Additional Staff
You're tasked with increasing your team's technical output tenfold without hiring new engineers.
What investments in automation, processes, or tooling would make this possible? How would you prioritize tasks and features to maximize impact with existing resources?
