Introducing our sensible defaults
Defaults are a starting point to create a sense of simplicity, and to reduce friction. They are not intended to be “best practices”, but rather a set of initial assumptions that we know to be effective and useful.
We all know the value of efficiency. Sensible defaults are our way of codifying best practices and principles into pre-defined approaches for common tasks.
Our sensible defaults stem from core values and principles, providing a foundation for good software delivery. While sometimes aspirational, they're often the essential building blocks for success.
We focus on these enduring principles, not specific tools, which tend to be fleeting. Tools support practices, but the underlying values ensure lasting effectiveness.
By adopting sensible defaults strategically, we can work smarter, not harder, and continue delivering exceptional results for our clients.
We leverage the collective knowledge to elevate our efficiency and collaboratively refine these defaults as we move forward.
Sensible defaults can reduce friction and provide simplicity anywhere one can think to apply them. They are the bedrock of minimalist practice and a quiet mind.
The sensible defaults playbook
Delivery practices and principles have historically spread through Thoughtworks through tribal knowledge and working together in co-located spaces. The accelerated pace of growth and move to remote working increases the need to capture and curate digital resources to support faster onboarding into teams and practices, and address the learning through interaction gap.
We believe by defining commonly agreed approaches for the ways we work we will increase delivery success and operational efficiency, reduce friction and increase cohesion for teams located in different geographic regions when working with clients.
Why we have sensible defaults
Defaults minimize repetitive decision-making, freeing up mental space for tackling complex challenges.
By minimizing upfront decision-making, defaults expedite workflows and keep projects moving forward.
Shared practices promote consistency, leading to smoother teamwork and predictable outcomes.
Clear defaults accelerate integration for new team members (both internal and client side)
Not a monolith, but a map
Defaults are a foundation, not a cage. We believe it is important to navigate them effectively.
- Embrace established practices. Utilize defaults for well-defined Thoughtworks practices proven to deliver value.
- Client-centric adaptation. Recognize that clients may not be ready for a complete methodology shift. Adapt defaults to their existing framework for a smoother onramp.
- Continuous improvement. Re-evaluate defaults regularly. Be prepared to adjust or abandon them as needed to stay innovative.
- Maintain flexibility. Defaults are a starting point, not a rigid rulebook. Be prepared to adjust based on project specifics and client needs.
- Avoid blind adherence. Don't let established defaults hinder innovation. Re-evaluate their effectiveness regularly and adapt or abandon them as necessary.
A note on GenAI
The field of GenAI is still in its early stages. While there are some efforts towards standardized practices and safety guidelines, widespread adoption of sensible defaults seems premature. Defaults might restrict the full potential of GenAI, hindering exploration and pushing boundaries and because GenAI is constantly evolving at such a pace, any defaults established are likely to quickly become outdated and stifle progress.
The more likely scenario is the ongoing use and development of a framework for 'sensible guardrails' instead of rigid defaults. Fostering a responsible and well-defined framework for its development and deployment is crucial. These guardrails would define safety boundaries, ethical considerations and transparent reporting mechanisms, while still allowing for customization and innovation.
