Serving Seattle, Puget Sound, and Washington State.
Welcome to the IIBA® Seattle Chapter

With over 29,000 Members, over 300 Corporate Members, and over 120 Chapters, International Institute of Business Analysis™ (IIBA®) is the recognized, non-profit association for business analysis professionals around the world.

As the voice of the business analysis community, IIBA® supports the recognition of the profession and works to maintain standards for the practice and certification.

IIBA-Seattle™ welcomes members from around Puget Sound and Washington state to share our talents and experience, assist with achieving IIBA® certification, and increase our community's knowledge, networks and connections.  

The Seattle chapter holds regular meetings at virtually and at various locations, with speakers, networking, and educational opportunities for members and non-members. 

Join Us on LinkedIn: https://www.linkedin.com/groups/118381/

Join Us on Meetup: ​https://www.meetup.com/Seattle-Business-Analysis-Agile-Practitioners/

Follow Us on X/Twitter: @SeattleIIBA

To sign into this chapter site, use your IIBA Global user name and password, the same one you use at iiba.org.

Sign Up for Our Mailing List

October 2026

S
M
T
W
T
F
S
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Analyst Catalyst Blog
Stakeholder-Informed vs. Validated: A Marketplace Case Study
Stakeholder feedback can identify genuine needs, but it doesn’t always reveal which needs will drive action. This case study explores how behavioural evidence led us to reassess acquisition priorities, feature context, and the assumptions behind our next experiment.
Your AI Can't Fix a Process You Haven't Looked At
On this episode of Business Analysis Live, Oge Nwachukwu explains why AI applied to a broken process just makes the brokenness happen faster.
AI-Assisted Prototyping: Turning Requirements Into Interaction
Comprehensive requirements documentation doesn't automatically create shared understanding. When stakeholders can interact with a working representation of the proposed solution while requirements are still being shaped, ambiguity surfaces earlier (and cheaper).