- handbook
- Company
- Company
- Board
- Communications
- Decision making
- Guides
- KPIs and OKRs
- principles
- Remote Work
- Security
- Asset Management Policy
- Business Continuity & Disaster Recovery Policy
- Data Management Policy
- Information Security Roles and Responsibilities
- Operations Security Policy
- Risk Management Policy
- Third-Party Risk Management Policy
- Human Resources Security Policy
- Access Control Policy
- Incident Response Plan
- Cryptography Policy
- Information Security Policy and Acceptable Use Policy
- Secure Development Policy
- strategy
- values
- Operations
- Product
- Feedback
- Metrics
- Node-RED Dashboard
- personas
- Pricing Principles
- Principles
- Product Categories
- Responsibilities
- Strategy
- Versioning
- Customer department
- Customer
- Hubspot
- Marketing
- How we work
- Marketing
- Video
- Boiler Plate Descriptions
- Marketing - Website
- Customer Stories
- Webinars
- Social Media
- blog
- Sales
- Engineering & Design Practices
- Design
- Engineering
- contributing
- Front End
- Packaging Guidelines
- Platform Ops
- Project Management
- Releases
- Security Policy
- tools
- Internal Operations
- People Ops
# How we make decisions
# Directly Responsible Individual
A DRI, also known as Directly Responsible Individual, is a method of assigning clear ownership and accountability for specific tasks, projects, or initiatives within an organization. The purpose of a DRI is to ensure that there is a single individual who is ultimately responsible for the success or failure of a particular undertaking.
When decisions need to be made regarding a DRI's area of responsibility, the DRI is the person who has the final say and is empowered to make those decisions. This allows for efficient decision-making and prevents decision paralysis or ambiguity within FlowFuse. The DRI is expected to gather relevant input and feedback from other stakeholders but is ultimately responsible for making the final call. Other stakeholders might need to Disagree and Commit. Regular (async) communication and collaboration with other team members and stakeholders is crucial to ensure alignment and support for the DRI's initiatives.
The appointment of a DRI occurs through the CEO or CTO. They will identify the areas of ownership and accountability within the organization and then assign the appropriate DRI. The selection of a DRI is based on factors such as expertise, experience, and the individual's ability to handle the specific task or project successfully.
Note that both the CEO and CTO retain the right to veto decisions. This should very seldomly happen.
DRI's weren't invented by FlowFuse, we stand on the shoulder of giants that championed the term and iterated before us. Read about the prior art: