Areas let you categorize development activity into groups that align with your roadmap, like organizational units, product divisions, or cross-functional teams.
Once defined, Macroscope automatically:
- Classifies all commit activity into the appropriate Area using codebase context, linked tickets, and IdP metadata
- Generates executive summaries for each Area, updated multiple times per day
- Enables Area-specific questions via the agent
- Sends Area-specific weekly email digests
If your team is fewer than 20 developers, you probably don’t need Areas. Macroscope treats your whole organization as a single Area by default and still generates executive summaries.
Executive Summaries
Macroscope generates executive summaries for each Area, displayed on the Home page and sent via weekly email digests.
Example Areas
- By org or business unit (e.g. Consumer Team, Revenue Team)
- By product strategy group (e.g. Code Review, Platform)
Writing Effective Descriptions
Macroscope uses your Area descriptions to classify commits, so detail matters. Include:
- Types of work that belong in this Area
- Specific terminology your team uses
- Team names associated with this Area
- Related systems, services, or products
Edit descriptions anytime on the Areas page.
Example
Area Name: Consumer Growth
**Overview:** The Consumer Growth team drives user acquisition and activation.
**Work in this Area:**
- User onboarding flows and tutorials
- Sign-up and authentication experiences
- Marketing landing pages and conversion funnels
- A/B testing frameworks for growth experiments
- Referral and invite systems
**Teams:** Growth Engineering, Consumer Acquisition, Onboarding Experience
**Related Systems:** Consumer web app, mobile sign-up, marketing website, email service, experimentation platform, analytics infrastructure
