|From The Guardian (https://static-secure.guim.co.uk/|
David Morris wrote an article called "We're All Designers Now" that is worth reading. My concerns with this approach isn't that it's wrong or misguided. I was the primary advocate for integrating the concepts of 'requirement' and 'design' in the Business Analysis Core Concept Model (BACCM) and ultimately in the BABOK Guide v3 Draft. What I'm saying is that we can confidently state that IIBA has taken the position that requirements and designs are different points of view on the same artifacts.
We can also confidently state that IIBA has not taken the position that Business Analysts (role) are Designers (role), or that Business Analysis (disciple) is Design (discipline).
I think a lot of the confusion in this question comes from the way the disciplines are named. Perhaps not surprisingly, the people who call themselves Designers named their profession based on the artifact they create. Also not surprisingly, Business Analysts have named their profession based on the reason we create artifacts. That should sound pretty familiar.
The design-side of the requirements-design spectrum is solution-oriented, exploring specific ways to realize potential value. The requirements-side of the requirements-design spectrum is need-oriented, exploring the nature of potential value that could be realized.
What I'm saying is that Designers need someone like David to write an article called "We're All Requirementortionists Now", to explain how 'design thinking' is very much what we call 'business analysis'.
Also, I'd like to change my title to 'Requirementortionist' because reasons.