Often a company knows that an area of the business needs to be improved, but they don't know exactly what needs to be done or how to go about it. They also appreciate that a consultant can bring a new perspective to enhance the knowledge that already exists in the corporation. A Business Analysis project can help a company define and quantify objectives, and then explore how information systems can be utilized to achieve these objectives.

A Business Analysis project usually goes through several steps. Not all steps are required for all projects, especially if the information already exists or the step will be performed by company personnel:

1. Define project scope and estimate costs.
2. Interview client regarding goals, objectives, and current environment. Help client develop SMART objectives, i.e. Specific, Measurable, Achievable, Realistic, and Timely.
3. Document goals and objectives.
4. Write a current state assessment that covers what has been tried in the past, what systems, interfaces and standards are currently in place, and what data is available and its quality.
5. Gather volume, profit, error, and other data related to measuring current performance. Organize data and calculate a baseline for the objectives. This step also assures that objectives are SMART.
6. Explore system alternatives (e.g. build vs. buy vs. status quo) to meet objectives.
7. Get input from client regarding system alternatives.
8. Develop system alternatives. The level of detail and type of information required varies from one project to the next, but may include sections on:
   - System governance
   - Different approaches to achieving the objectives, with pros and cons
   - System architecture
   - Different software products available with product summaries, pros and cons
   - Data requirements, including data schemas and information flows
   - Hardware and networking requirements
9. Do a cost benefit analysis for different approaches / software, and document non-monetary costs and benefits that pertain to objectives.
10. Present an interim report and incorporate feedback.
11. Present a final report.
12. Do a post implementation study to compare actual achievements with projected achievements, and document lessons learned.

Co-authored Systems Management Guidelines for use by clinics in Alberta to help them assess IT-related risks and put in place business practices (in particular, a comprehensive backup process) to mitigate these risks.

Co-authored a business requirements specification used to procure bids to design a Chronic Disease Management (CDM) System in the four western Canadian provinces; including sections summarizing the current state of CDM in each province, CDM best practices, the contextual and conceptual models (using Zachman Framework), a data entity model, and work flows modeled using Business Process Modeling Notation (BPMN).

Authored a business plan to implement distance learning for continuing education for the fifty thousand health care providers in Alberta, including sections enumerating educational services requirements, potential providers, personnel job descriptions, matrix outlining the stakeholders’ responsibilities, and and interactive Excel-based cost benefit analysis.

Authored a business plan to implement a data warehouse for clinical test results, including sections for technology, data, performance and operational requirements, system architecture, and cost benefit analysis.

Assisted in the preparation of a dozen health-care-related RFI and RFP documents.

Co-authored a plan to migrate a manufacturing company from custom written software and manual systems to an integrated business management system. Subsequently helped implement the software, including installing hardware and software, configuring and testing software, migrating data, and training users.