Explorations in Software Design

Software Fail Tip 27: Apples and Rutabagas

Why are there so many self-help articles being written? Where's the assistance for those who want to see their software development project fail miserably -- go way over budget, cause endless frustration for all involved, and end up with a partially functional end product that no one wants to use? Read on!


When Requirements Are Not Enough

As I consider examples from my development career that showcase the benefits of pre-production design, one example that frequently comes to my mind really drove home for me the concept that requirements documents are often not enough. I was the technical lead on a project for a major agricultural company. We had a client who had a time-intensive daily process management system that involved interacting with numerous spreadsheets.

Welcome to Fusion Software Design

Here at Fusion, we design software — visually (wireframes, mockups, prototypes).

The process starts with your team sharing a brain dump of the need, requirements, and context of your planned software. We digest the information and then start a process of sketching out wireframes that visualize the form and function of the application.

Download a free "software hero" guide today!

Read this guide before you start your next software project

Choose a responsibility:

Discuss Your Project

© 2024 Fusion Software Design