Analysis: the difference between actual & assumed
Our core practice. Everything we do is centered on analysis. How could it be otherwise? Gathering the requirements, comparing the technologies and vendors and selecting the CMS that drives one of the largest online retailers? How about three online retailers? That was us. Select the vendor to internationalize seven sites of the leading bio-tech manufacturer? We did that.
Effective business analysis demands intellectual curiosity with a desire for continuous testing and actionable change combined with a clarity of communication to spread your insights across the team. We’ve learned that the product of good analysis is clarity and simplicity, not complexity, jargon, and directories of hard to find and understand documentation. Over-specification produces inflexible processes which cannot accommodate the unexpected. We also believe that every piece of knowledge must have a single, unambiguous, authoritative representation within a system. Applying our philosophy, we’ve cut documentation overhead by two-thirds for some clients, and development errors by three-quarters. For this we have established tested and true best practices for documentation and collaboration tools for clients that are inexpensive and easy to implement as part of our end-to-end solution for project and development management and documentation.