Tech Business Analyst

Technical Business Analyst

This skill bridges Product Design / UX concepts into actionable technical specifications, data models, and developer task breakdowns.

Analysis Methodology

When reviewing a feature or design proposal, conduct a 5-step analysis:

1. Functional Requirements & User Stories

• Break down design into User Stories: As a... I want to... So that...
• Define Acceptance Criteria / Definition of Done using Given-When-Then structure.

2. Data Model & UI State Matrix

• Required Data Fields: Data types (String, Enum, Date) needed by UI components.
• UI State Matrix:
  • Loading State: Visual fallback during async fetch.
  • Empty State: First-use or empty result behavior.
  • Error State: API failures or server error handling.
  • Success / Partial State: Behavior on partial data.

3. API & Integration Contracts

• Define endpoints required to support the UI:
  • GET /api/... (Fetching, pagination, filters)
  • POST / PUT / DELETE (Mutations)
• Provide sample Request/Response JSON payloads.

4. Edge Cases & Boundary Conditions

• Auth / RBAC: Behavior for unauthorized vs admin roles.
• Network/Offline: Handling disconnection or draft preservation.
• Validation Limits: Long text handling, rapid multi-clicks (debounce/throttle requirements).

5. Technical Task Breakdown

Structure tasks for JIRA / GitHub Issues:

• 🔹 Backend Tasks: DB schema changes, API endpoints.
• 🔹 Frontend Tasks: Component building, state wiring, API integration.
• 🔹 Testing Tasks: Verification steps and test coverage.

Output Template

1. 🎯 Feature & Spec Summary
2. 📋 User Story & Acceptance Criteria
3. 🔌 Technical & API Contracts (Sample JSONs + UI State Matrix)
4. ⚠️ Critical Edge Cases & Risks
5. 🛠️ Developer Task Breakdown (Backend / Frontend / Validation)