💻 Technical Skills
Understanding systems, databases, and technology concepts
Data & Databases
HIGH Importance
What It Is
Understanding how data is organized, stored, and retrieved in systems. This includes basic SQL knowledge, data modeling, and how databases work.
What BAs Need to Know
- Basic SQL queries (SELECT, WHERE, JOIN)
- Database concepts (tables, relationships, normalization)
- Data types and validation
- Performance and indexing basics
- Data migration and integration concepts
Real-World Application:
You're gathering requirements for a new reporting feature. You need to understand where the data lives, how it's structured, and what performance impact a new query might have. You write a simple SQL query to validate your assumptions about the data, then discuss findings with developers.
System Architecture
HIGH Importance
What It Is
Understanding how software systems are designed, how components interact, and the trade-offs in different architectural approaches.
What BAs Need to Know
- Client-server vs. cloud architectures
- Microservices vs. monolithic applications
- API concepts and integrations
- Scalability and performance implications
- Security and infrastructure considerations
Real-World Application:
During a system upgrade project, the tech architect explains that moving to microservices will allow faster releases but requires new monitoring. You understand the implications and translate this into business context: faster features but higher operational costs. You help the business make an informed decision.
Security & Compliance
CRITICAL Importance
What It Is
Understanding security principles, compliance requirements (GDPR, HIPAA, PCI), and how to build secure systems.
What BAs Need to Know
- Relevant compliance frameworks for your industry
- Authentication and authorization concepts
- Data privacy and encryption basics
- Security requirements documentation
- Risk assessment and mitigation
Real-World Application:
In a healthcare system project, you document HIPAA compliance requirements. You ensure user access is role-based, data is encrypted, and audit trails are maintained. You include these in requirements and test plans to ensure compliance before go-live.
APIs & Integrations
HIGH Importance
What It Is
Understanding how systems communicate with each other through APIs (Application Programming Interfaces) and how to design integrations.
What BAs Need to Know
- API fundamentals (REST, SOAP, webhooks)
- Request/response formats (JSON, XML)
- Rate limiting and throttling
- Error handling and retries
- Integration testing strategies
Real-World Application:
You're integrating a new payment processor with your e-commerce system. You review the API documentation, understand the data format it expects, and work with developers to map your order data to the API requirements. You define how to handle payment failures and retries.
🔍 Analysis Skills
Decomposing problems and understanding complex business situations
Requirements Gathering
CRITICAL Importance
What It Is
The ability to extract, understand, and document what stakeholders need from a system. This is the foundation of BA work.
Key Techniques
- Conducting effective interviews and workshops
- Active listening and asking clarifying questions
- Identifying stated vs. actual needs
- Capturing both functional and non-functional requirements
- Prioritizing requirements with stakeholders
Real-World Application:
In a requirements gathering interview, a sales manager says "We need faster reporting." A good BA doesn't stop there. You ask: How fast? Which reports? Who uses them? What decisions does it drive? You uncover that they really need real-time dashboards for sales managers, not just faster reports. This distinction changes the entire solution.
Systems Thinking
CRITICAL Importance
What It Is
Understanding how different parts of a business and its systems interconnect, and how changes in one area affect others.
Key Techniques
- Creating system diagrams showing dependencies
- Identifying downstream impacts of changes
- Understanding end-to-end processes
- Thinking about edge cases and exceptions
- Considering long-term implications
Real-World Application:
Finance department asks you to automate invoice processing. But you think: invoices feed into accounting, which impacts GL reports, which drives month-end close. You understand that automating invoicing will cascade through multiple systems. You identify all dependencies and coordinate across departments.
Root Cause Analysis
HIGH Importance
What It Is
The ability to dig deep into problems to find the underlying cause rather than treating symptoms.
Key Techniques
- 5 Whys analysis (ask "why" repeatedly)
- Fishbone/Ishikawa diagrams
- Data analysis to find patterns
- Validating assumptions with evidence
- Distinguishing correlation from causation
Real-World Application:
Sales complains their system is "slow." Instead of saying "We need faster servers," you analyze: Which operations are slow? At what time? For which users? You discover only monthly reporting is slow, specifically when year-end data is involved. The real issue is poor query optimization, not server capacity.
Data Analysis & Visualization
HIGH Importance
What It Is
The ability to gather data, analyze it for insights, and present findings clearly to stakeholders.
Key Techniques
- Using Excel and BI tools (Tableau, Power BI)
- Creating dashboards and reports
- Identifying trends and patterns
- Using data to support recommendations
- Presenting findings to non-technical audiences
Real-World Application:
You're evaluating whether to implement a new customer portal. You gather data on customer support tickets, showing 60% are password resets that could be self-service. You create a dashboard showing time saved and cost reduction. With data backing your recommendation, executives approve the project.
💬 Communication Skills
Effectively conveying information to diverse audiences
Active Listening
CRITICAL Importance
What It Is
Truly hearing and understanding what someone is saying, including what they're not saying explicitly.
Key Techniques
- Making eye contact and giving full attention
- Taking notes without interrupting
- Asking clarifying questions
- Summarizing to confirm understanding
- Reading non-verbal cues (body language, tone)
Real-World Application:
A business user says "The system is too complicated." A poor listener might just make it simpler. An active listener asks: Which parts are complicated? For whom? What are they trying to accomplish? The real issue might be lack of training, not system design.
Clear Writing
CRITICAL Importance
What It Is
Documenting requirements, decisions, and processes in clear, unambiguous, professional language.
Key Techniques
- Using simple, direct language
- Avoiding jargon (or defining it clearly)
- Organizing logically with headers and sections
- Using examples to clarify complex concepts
- Proofreading for clarity and accuracy
Real-World Application:
Your requirements document is the contract between business and development. Ambiguous writing causes misunderstandings, delays, and rework. Clear writing like "Users can export reports to PDF, Excel, or CSV formats" prevents developers from guessing which formats to support.
Presentation & Storytelling
HIGH Importance
What It Is
Presenting findings, recommendations, and project updates in compelling, memorable ways.
Key Techniques
- Creating visual slides (not text walls)
- Tailoring content to your audience
- Starting with the key message upfront
- Using data and stories to support points
- Managing Q&A effectively
Real-World Application:
You're presenting a system upgrade to executives. Instead of diving into technical details, you start: "This upgrade will reduce our month-end close by 2 days, saving 40 hours of manual work monthly." You've led with business value. Then you present data supporting the recommendation.
Facilitation
HIGH Importance
What It Is
Guiding groups through discussions, workshops, and meetings to productive outcomes.
Key Techniques
- Setting clear agenda and objectives
- Managing dominant personalities
- Ensuring everyone is heard
- Keeping discussions on track
- Capturing decisions and action items
Real-World Application:
In a requirements workshop, the Finance Director keeps dominating while other departments stay quiet. A good facilitator says: "I want to make sure we hear from everyone. Sales, what are your requirements?" You ensure all perspectives are captured, not just the loudest voice.
🚀 Leadership & Influence
Leading without formal authority and driving organizational change
Stakeholder Management
CRITICAL Importance
What It Is
Building and maintaining positive relationships with all project stakeholders, managing their expectations, and gaining their buy-in.
Key Techniques
- Identifying all stakeholders and their interests
- Regular communication tailored to each group
- Managing conflicting interests diplomatically
- Building trust through transparency
- Keeping stakeholders engaged and informed
Real-World Application:
You're managing a system implementation affecting three departments. Finance wants cost control, Operations wants speed, HR wants minimal disruption. You don't just report to executives; you actively manage each stakeholder's concerns, explain trade-offs, and gain buy-in for the final approach.
Conflict Resolution
HIGH Importance
What It Is
Addressing disagreements between stakeholders and finding mutually beneficial solutions.
Key Techniques
- Listening to all sides without judgment
- Finding common ground and shared interests
- Proposing creative win-win solutions
- Escalating only when necessary
- Documenting agreements clearly
Real-World Application:
Development says a feature will take 6 weeks; Sales promised it in 2 weeks. Instead of picking sides, you analyze: Can we scope it smaller for Phase 1? Can we add features in Phase 2? You find a compromise: Launch MVP in 4 weeks, enhance in Phase 2. Both sides feel heard and agree.
Influence & Persuasion
HIGH Importance
What It Is
The ability to convince others of your perspective without formal authority through logic, data, and credibility.
Key Techniques
- Building credibility through expertise
- Using data and evidence to support positions
- Understanding what motivates different stakeholders
- Framing issues in terms of their priorities
- Building alliances and consensus
Real-World Application:
You think the company should migrate to cloud infrastructure, but leadership is hesitant about cost. You don't argue emotionally; you present data: current infrastructure costs, maintenance burden, scalability limitations. You show how cloud enables new features and reduces long-term costs. Your data-driven approach persuades them.
Change Management
HIGH Importance
What It Is
Helping organizations and people adapt to new systems, processes, and ways of working.
Key Techniques
- Understanding and addressing resistance to change
- Developing communication and training plans
- Creating champions for change within the organization
- Measuring and tracking adoption
- Supporting users through transition
Real-World Application:
You're implementing new project management software. Users resist because "the old way worked fine." You don't dismiss them. You explain benefits (better visibility, fewer status meetings), provide training, identify power users who become advocates, and provide support during transition. Change happens when people understand "why," not just "what."
🛠️ BA Tools & Technologies
Software and platforms that help BAs work effectively
Project & Work Management Tools
HIGH Importance
Common Tools
- Jira: Issue tracking, sprint planning, agile workflows
- Azure DevOps: Microsoft's platform for planning, tracking, delivery
- Monday.com, Asana: Visual project management platforms
- Confluence: Documentation and knowledge sharing
- Trello: Simple kanban boards for organizing work
Real-World Application:
You use Jira to create user stories, link them to epics, and track acceptance criteria. During sprint planning, you discuss with developers which stories are ready. You track progress, manage backlog, and communicate status to stakeholders through Jira dashboards.
Diagramming & Wireframing Tools
HIGH Importance
Common Tools
- Lucidchart, Draw.io: Flowcharts, process diagrams, system architecture
- Figma, Adobe XD: Wireframes and UI mockups
- Visio: Professional diagramming (enterprise standard)
- Miro: Collaborative whiteboarding and ideation
Real-World Application:
You use Lucidchart to create process flow diagrams showing current and future state workflows. You share them in workshops for stakeholder review. Developers use the diagrams to understand the process they need to automate. Wireframes in Figma show UI layout before development begins.
Analytics & BI Tools
MEDIUM Importance
Common Tools
- Tableau, Power BI: Dashboard creation and data visualization
- Excel: Data analysis, pivot tables, basic analytics
- Google Analytics: Web traffic and user behavior analysis
- SQL/Python: Data extraction and analysis for technical BAs
Real-World Application:
You use Power BI to create dashboards showing system usage, feature adoption, and performance metrics. You analyze support ticket data to identify which features cause the most problems. Data-driven insights help prioritize improvements.
Documentation Tools
HIGH Importance
Common Tools
- Confluence, Notion: Documentation wikis and knowledge bases
- Microsoft Word, Google Docs: Formal documentation and specifications
- GitBook, Markdown: Technical documentation for developers
- Swagger/OpenAPI: API documentation standards
Real-World Application:
You maintain a Confluence wiki with requirements, process documentation, decisions made, and lessons learned. Team members reference this throughout the project. After project close, it serves as institutional knowledge for future initiatives.
🏢 Domain Knowledge
Understanding the business and industry you work in
Industry-Specific Knowledge
HIGH Importance
What It Means
Understanding the specific business domain you work in—its processes, terminology, regulations, and competitive landscape.
Examples by Industry
| Industry | Key Knowledge Areas |
|---|---|
| Finance | Accounting principles, regulatory compliance, financial instruments, risk management |
| Healthcare | HIPAA compliance, clinical workflows, patient care processes, medical terminology |
| Retail | Inventory management, supply chain, customer loyalty, pricing strategies |
| Manufacturing | Production planning, quality control, lean principles, supply chain |
Real-World Application:
In healthcare, understanding HIPAA means you know exactly what data you can and can't log. You know clinical workflows so you understand how a new system affects patient care delivery. This domain knowledge prevents you from proposing solutions that look good technically but don't work in practice.
Continuous Learning
HIGH Importance
What It Means
The mindset and practice of constantly learning new skills, tools, methodologies, and business knowledge.
Ways BAs Learn
- Reading industry blogs and publications
- Attending conferences and webinars
- Taking online courses (BA certifications, technical skills)
- Learning from colleagues and mentors
- Reading and analyzing case studies
- Experimenting with new tools and methodologies
Real-World Application:
You notice your industry is shifting to AI/ML. You don't just ignore it. You take an online course on AI fundamentals, read about use cases in your industry, and start thinking about how AI could improve your products. When the company decides to add AI features, you're already knowledgeable and can speak intelligently with stakeholders.
Business Acumen
HIGH Importance
What It Means
Understanding business fundamentals: how your company makes money, its competitive position, and what drives profitability.
Key Concepts
- Revenue models and pricing strategies
- Cost structure and unit economics
- Customer segments and market positioning
- Competitive landscape
- Strategic goals and how projects support them
Real-World Application:
A new feature request comes in. You don't just ask "Is it technically feasible?" You ask: "Which customer segment will this serve? How many customers have this pain point? What's the ROI?" You understand which features drive revenue vs. which are nice-to-have. This business thinking makes you valuable.