---
title: "Accountability"
description: "2 posts about Accountability, summarised, each linking to the original."
---

# Accountability
> 2 posts about Accountability, summarised, each linking to the original.

## Articles

### [How California built its Behavioral Health Public County Profile on Databricks](https://yomu.fyi/post/how-california-built-its-behavioral-health-public-county-profile-on-da.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Michael Smith, Cameron Kahn, Stephen Hsu, Scott Black, Ben McKay, Varun Ganti
- Published: Oct 10, 2026
- Type: Explainer

The California Department of Health Care Services built the Behavioral Health Public County Profile on Databricks, a public dashboard consolidating behavioral health data from all 58 counties for nearly 40 million Californians. Launched on October 1, 2026, following the 2024 passage of Proposition 1, the dashboard supports the new Behavioral Health Services Act (BHSA) tying funding to statewide goals for outcomes, equity, and transparency. The platform uses Spark Declarative Pipelines and Lakeflow Connect for unified data ingestion, Semantic Views for standardized metrics across counties, and serverless compute to process data at scale without infrastructure management. It operates on a FedRAMP-authorized environment meeting federal security standards for health data, with data quality and lineage ensuring every number can be traced to its source. The County Profile enables public comparison of county plans, funding, service delivery, and performance measures, creating a feedback loop between policy intent and measurable outcomes for democratic oversight.


### [Product Teams: How to Build & Structure Product Teams for Growth](https://yomu.fyi/post/product-teams-how-to-build-amp-structure-product-teams-for-growth.md)
- Company: [Intercom](https://yomu.fyi/company/intercom.md)
- Published: Oct 8, 2026
- Type: Explainer

Intercom shares the process it used to scale its product team from a smaller size to four Product Managers, four Designers, and 25 Engineers over 12-18 months. The process is built on four areas: decision-making guidelines, clear role-based accountability, a lightweight transparent roadmap, and a culture of goal setting. The roadmap has three timeframes: solid releases for the next 4-6 weeks, planned high-level briefs for the following months, and speculative ideas beyond that. Accountability is assigned by role, with the PM responsible for problem analysis and success, the Designer for design quality, and the Engineering Lead for delivery and code quality. Teams set weekly goals tracked in an internal tool called Hustle and daily goals on whiteboards, with weekly demos every Friday to reinforce the cadence of building.