In this second episode of the Creating a Software Solution series we look at the clickable demo.  This tactic is used to help speed software design and becoming very common.  However, an effective clickable demo is much more than a wireframe.  We look at how to avoid spending too much time on details as well as how to keep it flexible.

A Fine Line between Throw-away and Beta

We started the series by looking at requirements and use cases.  This next step continues a focus on the “why” of the project.  We look at how an effective clickable demo is a first step in solving that core problem.  It is a visual tool for discussing details and even the user experience of the proposed solution.  Although we prefer not to throw work away, this demo must allow for that option. We look at what should be included in a demo and how to present it in ways that are most likely to promote re-use.  We also discuss the demo itself and how to tell a story in that presentation.


This series comes from our mentoring/mastermind classes.  These classes are virtual meetings that focus on how to improve our technical skills and build our businesses.  The goals of each member vary.  However, this diversity makes for great discussions and ton of educational value every time we meet.  We hope you enjoy this series as much as we enjoy creating it.

Slide Deck: Clickable Demo

Other classes you might consider:

Rob Broadhead

Rob is a founder of, and frequent contributor to, Develpreneur. This includes the Building Better Developers podcast. He is also a lifetime learner as a developer, designer, and manager of software solutions. Rob is the founder of RB Consulting and has managed to author a book about his family experiences and a few about becoming a better developer. In his free time, he stays busy raising five children (although they have grown into adults). When he has a chance to breathe, he is on the ice playing hockey to relax or working on his ballroom dance skills.

Leave a Reply