I wrote this paper at work to galvanize thoughts around ways to do my job that make systems development more efficient.  Back office big-data projects are different from customer facing UX driven ‘products’ and so we should think about the work in a different context.  Less is more.  80:20.  KISS.  All the typical euphemisms are thrown around but never actually followed.  Capability Based Design is a philosophy that helps the dev teams, funding sponsors, and business users act together for the benefit of the project and the organization.  It is how I have been thinking and doing my job for a while now.  I hope it rings true with others. I’d love to get feedback on how practical it might be from people in similar roles.

Capability Based Design