Skip to content
Leading Australian training company since 1989
facebook
twitter
youtube
linkedin
IRM Training Logo
Call Support 1300 819 078
Email Support training@irm.com.au
  • Home
  • About Us
    • About IRM Training
    • Testimonials
  • Courses
  • Locations
    • Brisbane
    • Canberra
    • Melbourne
    • Sydney
    • ‹ More Locations ›
  • Services
    • Public Training
    • In-House Training
    • Flexible Group Training
  • Certification
  • Resources
    • BABOK® Course Mapping
    • The BA’s Training Roadmap
    • Partners & Links
    • Articles »
      • The Role of Business Analysts in Cybersecurity Analysis
      • The Future of Business Analysis in the Age of AI
      • Business Analyst Salary & Job Trends – End of 2020 Review
      • Practical Training Delivered Remotely (Live)
      • Business Analyst Interviews
      • Introduction to Agile (and Scrum)
      • More…
  • Contact
  • Book Now

Separating Analysis from Design

Home > Uncategorized > Separating Analysis from Design

Separating Analysis from Design

12/04/2004 | By IRM Training
0

Looking at what business objectives you are trying to satisfy before leaping into the technology enables you to use the technology wisely, manage scope and cut costs, producing systems which work for your clients.

It’s easy to concentrate on the technical features of any project and lose sight of the reason for its existence. Every project exists to solve a problem. Either what you have doesn’t work well enough and needs improving, or you need to invent something totally new. After all, “If it ain’t broke, don’t fix it.”

Too often the pressures of deadlines and budgets lead us to bypass the important process of analysing business needs, and we leap straight into the technology. But how often do we find that the system doesn’t do exactly what’s required. Users are obliged to use workarounds, reducing some of the benefits we were supposed to provide which also affects our credibility. How often do we need to invest extra time and expense in providing Version 2 (and 3 and 4 and …), when some careful work might have exposed the real needs earlier?

 

Read full paper: Separating Analysis from Design

 


If you liked this paper, you may also enjoy:

Is Business Analysis Low Tech?

Solution Mode Thinking

Stakeholder Communications – Pictures not Words


 

Share this!
Share on print
Print
Share on email
Email
Share on linkedin
Linkedin
Share on google
Google
Share on twitter
Twitter

Tags: BA techniques, business analysis, business analysis tools, SDLC, waterfall

Previous Articles

  • Workshop Facilitation – How to Engage Quiet Participants
  • How to Create Use Cases
  • The Role of Business Analysts in Cybersecurity Analysis
  • The Future of Business Analysis in the Age of AI
  • Business Analyst Salary & Job Trends – End of 2020 Review
  • Practical Training Delivered Remotely (Live)
  • Business Analysis Industry Trends in 2019
  • Business Analyst Salary & Job Outlook
  • Business Analyst Interviews
  • Introduction to Agile (and Scrum)

Get in Contact

Phone: 1300 819 078

Email: training@irm.com.au

Online Contact Form

New Articles

  • Workshop Facilitation – How to Engage Quiet Participants
  • How to Create Use Cases
  • The Role of Business Analysts in Cybersecurity Analysis
  • The Future of Business Analysis in the Age of AI

Explore Topics

BPMN business analysis business analysis skills business analysis techniques business analyst business analyst training data flow diagrams interview techniques problem solving process modelling requirements gathering technical writing UML use cases user stories
© IRM Training Pty Ltd 2025 - ABN 56 007 219 589 | Terms & Conditions | Privacy Policy | FAQs