Motion is a methodology for project prioritization and selection.

Why Motion?

"Yesterday's tools (business architecture process mapping) were not designed to respond to today's needs (dynamic change) or tomorrow's promise (rapid innovation). More and more often, process and efficiency-based business improvement methodologies find themselves outflanked by the sheer rate of change. To resolve this problem and allow a business to reach its full potential, Microsoft challenged a team to look beyond current practices to the next generation of business philosophy, and to develop a business architecture methodology that could handle the present and coming challenges of the connected economy.

Capability architecture, not process architecture, is at the core of the Motion methodology. By initially abstracting processes and looking to business capability, you derive an inherently more stable view of your business. Business capability mapping allows for more control over a given function, because it blends the traditional process views with a strategic and tactical view of the organization. Exposing this "whole" view of your organization, called Motion Business Architecture, drives rapid and relevant decision making that is otherwise quite difficult to achieve."

I used to work in the CTO Office at Microsoft - which is where Motion began as an incubation effort - and my relationship with Motion goes back many years.