# Operating Model

## Team Structure

The Technical Solutions team is unique in the sense that it federates a very wide range of skills and expertise (inherent complexity of building software). Due to our team’s size, some domains of expertise are led by a single person, resulting in one-person teams. We see this as a temporary situation but find it necessary to formalize these teams as the services they provide are essential to our collective success.

<div drawio-diagram="16"><img src="https://wiki.cloud.akvo.org/uploads/images/drawio/2023-04/FHUUfRvoFS8Quwqt-drawing-3-1680593681.png" alt=""/></div>

The Technical Solutions team is composed of 2 types of teams:

- <span style="background-color: rgb(194, 224, 244);">Mission Teams</span> - They execute the core operational goals of Akvo, i.e. build software for impact.
- <span style="background-color: rgb(191, 237, 210);">Support Teams</span> - They provide centralized domain expertise that is required for the Mission teams to achieve their goals.
- <span style="background-color: rgb(236, 202, 250);">Hybrid Teams</span> - They execute the mission and provides support capacity to the organization

Each team is described in a table with the following attributes:

- Mandate - A summary of what the team does at/for Akvo
- Offers - The services that the team offers
- Needs - The information, tools and services needed for that team to deliver its function
- KPIs - The KPIs that will be used to measure the performance and success of the team. In some instances, we’ve also described a number of metrics that reflect the volume of work.
- Lead - The person accountable for the team
- Coordination - The frequency with which the coordination meeting is held.
- Task Tracking - The place where work is tracked and coordinated (Asana).

## Mission Teams

### TC Team

<div align="left" dir="ltr" id="bkmrk-tech-consultancy-tea"><table border="1" style="border-collapse: collapse; width: 100%; height: 1607.72px; border-width: 1px; border-style: solid;"><colgroup><col style="width: 25.3205%;" width="158"></col><col style="width: 74.6795%;" width="466"></col></colgroup><thead><tr style="height: 35.3906px;"><td colspan="2" style="height: 35.3906px; border-width: 1px;">Tech Consultancy Team

</td></tr></thead><tbody><tr style="height: 81.2188px;"><td style="height: 81.2188px; border-width: 1px;">**Mandate**

</td><td style="height: 81.2188px; border-width: 1px;">- Support the BD team in developing and closing deals
- Deliver high quality and on budget custom software solutions

</td></tr><tr><td style="border-width: 1px;">**Offers**

</td><td style="border-width: 1px;">BD

- Explore partnership collaboration
- ToR evaluation (Go, No Go)
- Technical proposal writing (Budgets, Timelines)
- Tech PoC for concepts provided by sector leads

  
Delivery

- Custom software solutions
- Software handover activities
- Maintenance and support

</td></tr><tr><td style="border-width: 1px;">**Needs**

</td><td style="border-width: 1px;">Information

- BD - ToR, context
- Delivery - ToR, context, user requirements

  
Tools

- Capacity Planner
- PMT
- Task Manager
- Code hosting: Github
- CI/CD Pipeline: Semaphore, CircleCI
- Unit testing: coveralls

  
Services

- Hosting
- Design
- Testing
- User support

</td></tr><tr><td style="border-width: 1px;">**KPIs**

</td><td style="border-width: 1px;">Execution Efficiency

- Definition: Ability to execute the scope within the allocated budget
- Source: PMT
- Target: 100%

  
Team Utilization

- Definition: Ratio between allocated work days and available days to work
- Source: Capacity Planner
- Target: 90%

  
Team Billability

- Definition: Ratio between allocated work days on client projects and available days to work
- Source: Capacity Planner
- Target: 75%

  
Unit Test Coverage

- Definition: % of the code covered by unit tests
- Source: [Coveralls](https://coveralls.io/)
- Target: 80%

  
Integration Test Coverage

- Definition:
- Source: Integration testing software
- Target:

  
User reported bugs

- Definition: number of bugs reported by users after the software went into productions (by severity)
- Source: Freshdesk
- Target: less than 5% [critical bugs](https://docs.google.com/document/d/1YzfddH6VSAy2z7B5K-Xer02d3VZ9m2PDwwTlvA1iVMM/edit#heading=h.cy7blqjbt7qi)

</td></tr><tr style="height: 35.3906px;"><td style="height: 35.3906px; border-width: 1px;">**Lead**

</td><td style="height: 35.3906px; border-width: 1px;">[<span data-rich-links="{"per_n":"Joy Ghosh","per_e":"joy@akvo.org","type":"person"}">Joy Ghosh</span>](mailto:joy@akvo.org)

</td></tr><tr><td style="height: 103.609px; border-width: 1px;">**Coordination**

</td><td style="height: 103.609px; border-width: 1px;">- Project issue board on GH
- 3 times a week tasks status / adhoc as required
- Bi-weekly team status check

</td></tr><tr style="height: 35.3906px;"><td style="height: 35.3906px; border-width: 1px;">**Task Tracking**

</td><td style="height: 35.3906px; border-width: 1px;">Each project has its own Asana Team or Project

</td></tr></tbody></table>

</div>### Product Teams

<div align="left" dir="ltr" id="bkmrk-product-teams-mandat"><table border="1" style="border-collapse: collapse; width: 100%; height: 1343.13px; border-width: 1px; border-style: solid;"><colgroup><col style="width: 25.3399%;" width="158"></col><col style="width: 74.6601%;" width="466"></col></colgroup><thead><tr style="height: 29.7969px;"><td colspan="2" style="height: 29.7969px; border-width: 1px;">Product Teams</td></tr></thead><tbody><tr><td style="border-width: 1px;">**Mandate**

</td><td style="border-width: 1px;">- Build, maintain and provide user support of current Akvo products (FLOW, RSR).
- Develop new products based on market needs.

</td></tr><tr style="height: 81.2188px;"><td style="height: 81.2188px; border-width: 1px;">**Offers**

</td><td style="height: 81.2188px; border-width: 1px;">- Product development
- Product management

</td></tr><tr><td style="border-width: 1px;">**Needs**

</td><td style="height: 452.766px; border-width: 1px;">Information

- Market data
- User feedback

  
Tools

- Capacity Planner
- PMT
- Task Manager
- Code hosting: Github
- CI/CD Pipeline: Semaphore, CircleCI
- Unit testing: coveralls

  
Services

- Hosting
- Design
- Testing
- User support

</td></tr><tr><td style="height: 580.75px; border-width: 1px;">**KPIs**

</td><td style="height: 580.75px; border-width: 1px;">Bug Reports

- Definition: number of bugs reported by clients
- Source: Freshdesk
- Target: less than 5% [critical bugs](https://docs.google.com/document/d/1YzfddH6VSAy2z7B5K-Xer02d3VZ9m2PDwwTlvA1iVMM/edit#heading=h.cy7blqjbt7qi)

  
User Engagement

- Definition: This metric measures how often users are using the product and how engaged they are with it.
- Source: TDB
- Target: TBD

  
Revenue

- Definition: This metric tracks the amount of money generated by the product
- Source: Contracts
- Target:

  
Customer Satisfaction

- Definition: This metric measures how satisfied users are with the product.
- Source: Satisfaction questionnaires
- Target: 4/5 in average

</td></tr><tr style="height: 35.3906px;"><td style="height: 35.3906px; border-width: 1px;">**Lead**

</td><td style="height: 35.3906px; border-width: 1px;">[<span data-rich-links="{"per_n":"Guillaume Deflaux","per_e":"guillaume@akvo.org","type":"person"}">Guillaume Deflaux</span>](mailto:guillaume@akvo.org)

</td></tr><tr style="height: 35.3906px;"><td style="height: 35.3906px; border-width: 1px;">**Coordination**

</td><td style="height: 35.3906px; border-width: 1px;">Every 2 weeks - [<span data-rich-links="{"per_n":"Guillaume Deflaux","per_e":"guillaume@akvo.org","type":"person"}">Guillaume Deflaux</span>](mailto:guillaume@akvo.org) [<span data-rich-links="{"per_n":"Zuhdil Kurnia","per_e":"zuhdil@akvo.org","type":"person"}">Zuhdil Kurnia</span>](mailto:zuhdil@akvo.org)

</td></tr><tr style="height: 57.7812px;"><td style="height: 57.7812px; border-width: 1px;">**Task Tracking**

</td><td style="height: 57.7812px; border-width: 1px;">[RSR Project in Asana](https://app.asana.com/0/1203984935859136/board)

[FLOW Project in Asana](https://app.asana.com/0/1204279546124153/board)

</td></tr></tbody></table>

</div>## Support Teams

### DevOps Team

<div align="left" dir="ltr" id="bkmrk-devops-team-mandate-"><table border="1" style="border-collapse: collapse; width: 100%; height: 1710.88px; border-width: 1px; border-style: solid;"><colgroup><col style="width: 25.3399%;" width="158"></col><col style="width: 74.6601%;" width="466"></col></colgroup><thead><tr style="height: 35.3906px;"><td colspan="2" style="height: 35.3906px; border-width: 1px;">DevOps Team

</td></tr></thead><tbody><tr style="height: 81.2188px;"><td style="height: 81.2188px; border-width: 1px;">**Mandate**

</td><td style="height: 81.2188px; border-width: 1px;">- Secure internal and external systems
- Provide best-in-class infrastructure for the services Akvo offers

</td></tr><tr><td style="border-width: 1px;">**Offers**

</td><td style="border-width: 1px;">Security for internal and external systems (Company-wide)

- Implement security best practices for our internal tools (email, password management, etc…) and server deployments.

  
Infrastructure (TC Platforms / Products)

- Design
- Deployment
- Support &amp; Monitoring
- Costing

  
Knowledge Management &amp; Company Culture

- Updated technical documentation (wiki) covering the above topics (SOPs, best practices, …)
- Provide DevOps &amp; Security trainings internally
- Promote a DevOps &amp; Security culture
- Domain technical watch (best practices, tools, …)

</td></tr><tr><td style="border-width: 1px;">**Needs**

</td><td style="border-width: 1px;">Information

- Product/project software architecture plan (before development started)
- Product/project software architecture documentation
- Product/project system requirements and quickstart documentation
- Infrastructure budget allocation plan from product, project or BD team

  
Tools

- Hosting provider (Google Cloud, Contabo, Siteground)
- Code Version Control (Github)
- CI/CD Tools (SemaphoreCI, CircleCI, Github Action)
- Documentation tools
- Infrastructure orchestration and configuration management tools (Terraform, Ansible)
- Secret management tools (Hashicorp Vault, Vaultwarden)
- Maling tools (Mailjet)
- Workflow automation (N8N)

  
Services

- Testing

</td></tr><tr><td style="border-width: 1px;">**KPIs**

</td><td style="border-width: 1px;">Average Service Availability

- Definition: The client facing service are available
- Target: 99.9% over a quarter
- Source: Uptime checks

  
Change Success Rate

- Definition: Changes made by the DevOps team do not result in any downtime or other issues.
- Target: 90% over a quarter
- Source: uptime checks, CI/CD
- Note: downtime caused by deployments are not taken into account

  
Cost

- Definition: Amount that we spend on cloud services (mostly GCP)
- Target: Yearly targets based usage of services ([COGS](https://www.investopedia.com/terms/c/cogs.asp), cost per project…). Still TBD

  
Team Satisfaction

- Definition: The DevOps team should aim for a high level of satisfaction among internal teams who rely on DevOps support.
- Target: Score at least 8 out of 10 on average
- Source: Quarterly survey

</td></tr><tr style="height: 35.3906px;"><td style="height: 35.3906px; border-width: 1px;">**Lead**

</td><td style="height: 35.3906px; border-width: 1px;">[<span data-rich-links="{"per_n":"Anjar Fiandriato","per_e":"anjar@akvo.org","type":"person"}">Anjar Fiandriato</span>](mailto:anjar@akvo.org)

</td></tr><tr style="height: 35.3906px;"><td style="height: 35.3906px; border-width: 1px;">**Coordination**

</td><td style="height: 35.3906px; border-width: 1px;">Every 2 weeks - [<span data-rich-links="{"per_n":"Guillaume Deflaux","per_e":"guillaume@akvo.org","type":"person"}">Guillaume Deflaux</span>](mailto:guillaume@akvo.org) [<span data-rich-links="{"per_n":"Anjar Fiandriato","per_e":"anjar@akvo.org","type":"person"}">Anjar Fiandriato</span>](mailto:anjar@akvo.org)

</td></tr><tr style="height: 35.3906px;"><td style="height: 35.3906px; border-width: 1px;">**Task Tracking**

</td><td style="height: 35.3906px; border-width: 1px;">[DevOps Project in Asana](https://app.asana.com/0/1204279546124164/board)

</td></tr></tbody></table>

</div>### Design Team

<div align="left" dir="ltr" id="bkmrk-design-team-mandate-"><table border="1" style="border-collapse: collapse; width: 100%; height: 1225.42px; border-width: 1px; border-style: solid;"><colgroup><col style="width: 25.3399%;" width="158"></col><col style="width: 74.6601%;" width="466"></col></colgroup><thead><tr style="height: 35.3906px;"><td colspan="2" style="height: 35.3906px; border-width: 1px;">Design Team

</td></tr></thead><tbody><tr style="height: 58.8281px;"><td style="height: 58.8281px; border-width: 1px;">**Mandate**

</td><td style="height: 58.8281px; border-width: 1px;">- Support TC and product teams in delivering designed-for-purpose applications

</td></tr><tr style="height: 537.781px;"><td style="border-width: 1px; height: 537.781px;">**Offers**

</td><td style="border-width: 1px; height: 537.781px;">Requirements Gathering

- Conduct user research
- Collaborate with product managers, developers, and subject matter experts to define and prioritise user stories and product requirements

  
Wireframing &amp; UI Design

- Create wireframes, prototypes, and high-fidelity mockups that effectively communicate design concepts and interactions
- Create and maintain design style guides and design systems that support consistent and efficient design
- Provide corresponding HTML/CSS templates

  
User Feedback

- Continuously iterate on designs based on user feedback, stakeholder input, and usability testing

  
Knowledge Management &amp; Company Culture

- Updated technical documentation (wiki) covering the above topics (best practices, tools, …)
- Domain technical watch (best practices, tools, design trends, …)

</td></tr><tr style="height: 170.781px;"><td style="border-width: 1px; height: 170.781px;">**Needs**

</td><td style="border-width: 1px; height: 170.781px;">- User Research Tools
- Design and Prototyping Tools
- Collaboration Tools
- Design Systems and Style Guides
- Feedback and Iteration Tools
- Training and Professional Development

</td></tr><tr style="height: 316.469px;"><td style="height: 316.469px; border-width: 1px;">**KPIs**

</td><td style="height: 316.469px; border-width: 1px;"> **Process Indicators**

Projects use Design Process Checklist

- Target: 80%
- Source: Design Process Checklists

**Output Indicators**

% Completion of Design Process Checklist

- Target: 100%
- Source: Design Process Checklists

% Successful Task Completion (prototypes)

- Target: 80%
- Source: Maze

User Perceived Experience (prototypes)

- Target: 4/5
- Source: Maze

</td></tr><tr style="height: 35.3906px;"><td style="height: 35.3906px; border-width: 1px;">**Lead**

</td><td style="height: 35.3906px; border-width: 1px;">[<span data-rich-links="{"per_n":"Ouma Odhiambo","per_e":"ouma@akvo.org","type":"person"}">Ouma Odhiambo</span>](mailto:ouma@akvo.org)

</td></tr><tr style="height: 35.3906px;"><td style="height: 35.3906px; border-width: 1px;">**Coordination**

</td><td style="height: 35.3906px; border-width: 1px;">Every 2 weeks - [<span data-rich-links="{"per_n":"Guillaume Deflaux","per_e":"guillaume@akvo.org","type":"person"}">Guillaume Deflaux</span>](mailto:guillaume@akvo.org) [<span data-rich-links="{"per_n":"Ouma Odhiambo","per_e":"ouma@akvo.org","type":"person"}">Ouma Odhiambo</span>](mailto:ouma@akvo.org)

</td></tr><tr style="height: 35.3906px;"><td style="height: 35.3906px; border-width: 1px;">**Task Tracking**

</td><td style="height: 35.3906px; border-width: 1px;">[Design Project in Asana](https://app.asana.com/0/1204279546124171/board)

</td></tr></tbody></table>

</div>### User Support &amp; Quality Team

<div align="left" dir="ltr" id="bkmrk-user-support-%26-quali-1"><table border="1" style="border-collapse: collapse; width: 100%; border-width: 1px; border-style: solid;"><colgroup><col style="width: 25.3399%;" width="158"></col><col style="width: 74.6601%;" width="466"></col></colgroup><thead><tr><td colspan="2" style="border-width: 1px;">User Support &amp; Quality Team

</td></tr></thead><tbody><tr><td style="border-width: 1px;">**Mandate**

</td><td style="border-width: 1px;">- Be the first point of contact of our end-users and help them make the most of our platforms and products.
- Support the TC and products teams in delivering well tested software applications.

</td></tr><tr><td style="border-width: 1px;">**Offers**

</td><td style="border-width: 1px;">All the services are provided to Products and TC Platforms alike.

  
L1 Support

- First point of contact with users
- Triage issues and escalate if necessary
- Resolve issues that are related to the usage of the software (anything that is not a bug or a server issue)

  
User Trainings

- Create training curriculums
- Deliver trainings to end-users (remote/onsite)

  
Functional Testing

- Write test plans
- Execute test plans (automated or not)
- Document issues and create test reports

  
User Documentation

- Create and update user documentation inline with software release cycles.

  
Knowledge Management &amp; Company Culture

- Updated technical documentation (wiki) covering the above topics (best practices, tools, …)
- Domain technical watch (best practices, tools, …)

</td></tr><tr><td style="border-width: 1px;">**Needs**

</td><td style="border-width: 1px;">Information

- Platform/Product onboarding from the development teams
- Functional requirements documents
- User stories and personas
- Release schedules
- Test data
- Test environment

  
Tools

- Helpdesk (Freshdesk)
- Documentation/Wiki (Freshdesk, Bookstack)
- Automated Testing (Selenium, Appium)
- Test Management (TestRail, TestLodge, Zephyr, Zebrunner)
- Bug Tracking(Github, Asana)
- Load Testing (Gatling, Locust, LoadRunner)
- User Feedback (Piwik, HotJar, ProductBoard)

</td></tr><tr><td style="border-width: 1px;">**KPIs**

</td><td style="border-width: 1px;">L1 Support

- KPI
    
    
    - Definition: Number and % of tickets that breached the SLAs
    - Source: Freshdesk
    - Target: 0(%)
    
    
    - Definition: Level of satisfaction of users after the handling of their tickets
    - Source: Freshdesk
    - Target: 4/5 or higher
- SLA breaches
- Average User satisfaction Level

- Work Volume
- Number of tickets received (Freshdesk)
- Number / % of escalated tickets (L2+) (Freshdesk)
- Average first response time (Freshdesk)
- Average resolution time (Freshdesk)


  
User Trainings

- KPI
    
    
    - Definition: Declared level of satisfaction of trainees after a training on one of our platforms or products
    - Source: Post training questionnaire
    - Target: 4/5 or higher
- Average trainee satisfaction Level

- Work Volume
- Number of trainings delivered
- Number of created training curriculums
- Number of updated training curriculums


  
Functional Testing

- KPI
- TBD

- Work Volume
- Number of test plans written
- Number of test plans executed
- Number of test reports written


  
User Documentation

- KPI
    
    
    - Definition: The % of documentation sites that have content that cover 100% of the user facing features of platforms and products
    - Source: Documentation sites + platform / product release notes
    - Target: 100%
    
    
    - Definition: Level of helpfulness of documentation pages
    - Source: MkDocs
    - Target: 4/5 or higher
- % of up-to-date documentation sites
- User Satisfaction Level

- Work Volume
- Number of updated articles (MkDocs)
- Number of visits to the help sites (Piwik)


  
Knowledge Management &amp; Company Culture

- KPI
    
    
    - Definition: % of TC Platforms/Products using the documentation site and testing tools.
    - Source: Documentation sites + testing tools
    - Target: 100%
- Adoption

- Work Volume
- Number of significant updates to the wiki (Wiki)


</td></tr><tr><td style="border-width: 1px;">**Lead**

</td><td style="border-width: 1px;">[<span data-rich-links="{"per_n":"Jonah Kisioh","per_e":"jonah@akvo.org","type":"person"}">Jonah Kisioh</span>](mailto:jonah@akvo.org)

</td></tr><tr><td style="border-width: 1px;">**Coordination**

</td><td style="border-width: 1px;">Every 2 weeks - [<span data-rich-links="{"per_n":"Guillaume Deflaux","per_e":"guillaume@akvo.org","type":"person"}">Guillaume Deflaux</span>](mailto:guillaume@akvo.org) [<span data-rich-links="{"per_n":"Jonah Kisioh","per_e":"jonah@akvo.org","type":"person"}">Jonah Kisioh</span>](mailto:jonah@akvo.org)

</td></tr><tr><td style="border-width: 1px;">**Task Tracking**

</td><td style="border-width: 1px;">[Support &amp; Quality Project in Asana](https://app.asana.com/0/1204279546124178/board)

</td></tr></tbody></table>

</div>## Hybrid Teams

### Technical Solutions Management

<div align="left" dir="ltr" id="bkmrk-technical-solutions--1"><table border="1" style="border-collapse: collapse; width: 100%; border-style: solid;"><colgroup><col style="width: 25.3399%;" width="158"></col><col style="width: 74.6601%;" width="466"></col></colgroup><thead><tr><td colspan="2">Technical Solutions Management

</td></tr></thead><tbody><tr><td>**Mandate**

</td><td>- Align objectives of the Tech Solutions Team with the objectives of the rest of the company
- Improve the efficiency of the entire Tech Solutions Team

</td></tr><tr><td>**Offers**

</td><td>Strategic and technical orientations to sub teams, including tie-breaking based on suggestions. Internal initiatives to focus on:

- Resourcing
- Team / HR
- Tech Stack
- Methodology
- Tooling
- Quality Standards
- OKRs

</td></tr><tr><td>**Needs**

</td><td>Information

- Company strategy and objectives
- Feedback from sub teams

</td></tr><tr><td>**KPIs**

</td><td>Objective alignment

- Definition: The fact that the Technical Solutions sub team objectives are aligned with larger company objectives.

Team Efficiency

- Definition: The fact that the Technical Solutions sub team objectives create efficiencies that affect the entire team.

</td></tr><tr><td>**Lead**

</td><td>[<span data-rich-links="{"per_n":"Guillaume Deflaux","per_e":"guillaume@akvo.org","type":"person"}">Guillaume Deflaux</span>](mailto:guillaume@akvo.org)

</td></tr><tr><td>**Coordination**

</td><td>Monthly - [<span data-rich-links="{"per_n":"Guillaume Deflaux","per_e":"guillaume@akvo.org","type":"person"}">Guillaume Deflaux</span>](mailto:guillaume@akvo.org) [<span data-rich-links="{"per_n":"Joy Ghosh","per_e":"joy@akvo.org","type":"person"}">Joy Ghosh</span>](mailto:joy@akvo.org) [<span data-rich-links="{"per_n":"Deden Bangkit","per_e":"deden@akvo.org","type":"person"}">Deden Bangkit</span>](mailto:deden@akvo.org)

</td></tr><tr><td>**Task Tracking**

</td><td>[Internal Project in Asana](https://app.asana.com/0/1204279547424392/board)

</td></tr></tbody></table>

</div>## Coordination Mechanisms

Team coordination plays a big part in creating the right environment for our team to deliver great work and to create a positive dynamic. The team coordination approach described below aims to foster team building while boosting our collective efficiency, i.e. provide enough context for everyone to properly execute their work while doing so in a friendly, respectful and engaging manner.

This approach is purposely built for our current team. We should expect it to change should our team size and structure evolve.

### 1-to-1s Guillaume / Team Leads

In most instances these meetings are used both for people management and team coordination purposes.

<div align="left" dir="ltr" id="bkmrk-frequency-every-2-we"><table border="1" style="border-collapse: collapse; width: 100%; border-style: solid;"><colgroup><col width="157"></col><col width="467"></col></colgroup><tbody><tr><td>**Frequency**

</td><td>Every week

</td></tr><tr><td>**Duration**

</td><td>30 min

</td></tr><tr><td>**Purpose**

</td><td>- Ensure that there is a space to discuss your life at Akvo.
- Coordinate the definition and the execution of team roadmaps
- Ensure coherence of team specific initiatives within the larger Tech Solutions Team

</td></tr><tr><td>**Structure**

</td><td>Manager-Direct 1-to-1

- Workplate &amp; Projects
- Growth
- Performance

  
Team Specific Discussion

- Services
- Initiatives
- Roadmap
- Performance

</td></tr></tbody></table>

</div>### Tech Solutions All Hands

<div align="left" dir="ltr" id="bkmrk-frequency-every-2-we-1"><table border="1" style="border-collapse: collapse; width: 100%; border-style: solid;"><colgroup><col width="157"></col><col width="467"></col></colgroup><tbody><tr><td>**Frequency**

</td><td>Every 2 weeks

</td></tr><tr><td>**Duration**

</td><td>1h

</td></tr><tr><td>**Purpose**

</td><td>- Make sure that we can have a bit of “face time” all together in order to break the silos created by our day-to-day
- Create a space for direct communications with the entire team (email remains the official channel for team wide announcements)
- Create an experience sharing space to foster ideation and innovation within the Tech Team

</td></tr><tr><td>**Structure**

</td><td>Think Tank Thursdays (30 min)

- A rotating presentation by someone from the team.
- Any topic that is (vaguely) related to our work
- Any format allowed as long as there’s at least 10 min for questions. The more interactive the better.

  
All Hands (30 min)

- Team wide announcements
- Project / Product updates
- Team Specific Updates
- Updates from MC

</td></tr></tbody></table>

</div>