Using Claude.ai as Your BA Thinking Partner

Claude.ai vs. Document Generation

Most BAs initially use AI as a faster typewriter — paste requirements notes, get a formatted document. This is legitimate and valuable, but it leaves the most powerful use case unexplored.

Claude.ai's reasoning capabilities make it a genuine thinking partner for analysis work — not just drafting. The difference:

Document generation (AI as typewriter):

• Input: raw notes → Output: formatted document
• Value: time savings on mechanical work

Analysis support (AI as thinking partner):

• Input: problem or requirements set → AI challenges, extends, and critiques
• Value: catches gaps and assumptions that would create rework later

Assumption Testing

Every requirements document contains unstated assumptions. Some are harmless; others, when violated by the actual implementation, generate significant rework. Finding them early is one of the highest-value BA activities.

Here are the functional requirements for the accounts payable
automation system: [paste requirements]

Act as a skeptical business analyst reviewing this requirements set.

Identify:
1. Unstated assumptions — things that must be true for these
   requirements to work but are never stated
2. Requirements that conflict with each other
3. Edge cases that the requirements don't address
4. Business rules that are implied but not made explicit
5. Questions a developer would ask that the requirements don't answer

Be specific — reference requirement numbers. Don't be diplomatic
about gaps — flag every concern you find.

The "don't be diplomatic" instruction matters. By default, AI tends toward a collaborative, balanced tone that can soften the directness of critical feedback. For analysis purposes, you want exhaustive identification of problems, not a balanced assessment.

Stakeholder Impact Analysis

When a proposed requirement or change is introduced, a thorough BA thinks through the downstream impacts across all affected parties. This is time-consuming to do manually across complex organizations.

A new regulatory requirement mandates that all invoices
over $50,000 require a third approval level from the CFO
before payment, effective in 90 days.

The current AP system has a two-level approval workflow.

Analyze the impact of this change on:
1. The finance operations team's workload and workflow
2. The AP automation system requirements (what changes)
3. The ERP integration (what data must now flow differently)
4. Supplier relationships (payment timing implications)
5. Audit and compliance documentation requirements
6. System testing requirements (what new test cases are needed)

For each area: describe the impact and flag it as
HIGH/MEDIUM/LOW based on implementation effort.

This produces an impact assessment that would typically take a BA a full day to assemble — ready for review and stakeholder communication in minutes.

Alternative Analysis

When multiple approaches exist for meeting a requirement, a BA presents options with trade-offs to decision-makers. AI can construct balanced alternative analyses efficiently.

The AP automation project needs to integrate with the company's
existing SAP ERP system. Three approaches are being considered:

Option A: Real-time API integration
Option B: Nightly batch file transfer
Option C: Manual dual-entry with monthly reconciliation

Analyze these options for the following criteria:
- Implementation complexity
- Data freshness (how current is AP data in each system)
- Error detection and recovery
- Ongoing maintenance burden
- Risk if the ERP system is unavailable

Format: comparison table + 2-paragraph recommendation
for a mid-size company with a 4-person IT team.

The recommendation framing ("for a mid-size company with a 4-person IT team") is critical — it prevents generic analysis and grounds the output in the actual organizational context.

Risk Identification

Requirements risk analysis — identifying what could go wrong with the proposed solution — is a core BA responsibility that often gets compressed by deadline pressure.

Here is the requirements scope for the AP automation project:
[paste scope/requirements]

Perform a requirements risk analysis. For each risk:
- Risk description
- Root cause (why this risk exists)
- Potential impact if the risk materializes
- Likelihood: HIGH/MEDIUM/LOW
- Mitigation approach (what the BA team can do to reduce the risk)

Categories to cover:
- Requirements completeness (what we might have missed)
- Stakeholder alignment (where stakeholders might not agree)
- Technical feasibility assumptions (what might not be buildable as specified)
- Organizational change risks (process or cultural resistance)
- Integration risks (dependencies on other systems)

Using Claude for Difficult Stakeholder Situations

Some of the most valuable BA work is navigating difficult stakeholder situations — conflicting priorities, scope disputes, executive mandates that conflict with user needs. Claude can help prepare for these.

I have a stakeholder meeting tomorrow where I need to resolve
a conflict between two department heads:

Finance Director: wants all invoices routed through a central
approval queue regardless of amount
AP Manager: wants invoices under $5,000 to auto-approve
to reduce their team's workload

Both have valid positions. The executive sponsor hasn't weighed in.
The project is 6 weeks from go-live.

Help me prepare:
1. What is the strongest argument for each position?
2. What is a potential compromise that might satisfy both?
3. What questions should I ask to understand each stakeholder's
   underlying concern (not just their stated position)?
4. What are the implementation implications of each option?
   I need to present these factually, not advocate for one.

This turns a stressful stakeholder meeting into a prepared facilitation exercise.

Key Takeaways

• Claude.ai's highest BA value is as a thinking partner for analysis, not just a document generator
• Assumption testing, impact analysis, alternative analysis, and risk identification are all high-value use cases
• "Don't be diplomatic" — instruct AI to be exhaustive and direct when identifying problems, not balanced
• Always anchor analysis to your specific context (organization size, constraints, timelines) to prevent generic output
• Stakeholder situation preparation is a high-ROI use case: Claude helps you enter difficult meetings with a prepared, balanced position

---

Practice: Take a requirements decision or stakeholder conflict from your current or a recent project. Use Claude to perform an assumption test on the requirements involved. Compare what it identifies against what you know about the situation. Note where its analysis was correct, where it missed organizational context, and whether it identified anything you hadn't considered.