UI Experience Specificiation

Our User Interface Experience Specifications are different from traditional written functional specifications.

We believe that by starting with the visual design and then the programming, it will result in a more successful project.

What we can do for you

1. Build a UI Experience Specification for your project

   We can work with your management team, development team and design team and produce a complete UI Experience Specification for your project.

Written Functional Specifications - the WRONG way round

The traditional functional specification process is to write description of the user experience in a document, give that to the development team, and at the latter stage of the project introduce a user interface designer.

We think that’s the wrong way round.

Our way: Let people visualise first

We design the interface first. We want everyone looking at the user interface before a single line of code is written.

Words are open to interpretation. Whilst people may agree on paragraphs of text, very often they are thinking something different.

Images and interfaces are a common ground. People can see how the pages are laid out, how the data is presented, and see the user experience.

We still include words!

Of course it’s impossible for a thorough specification not to include words, diagrams, and use cases.

Our User Interface Experience Specification includes ‘The Big Picture’ which is a two page outline of the system, main functions, etc.

We then details all object relationships, permissions and use cases within the final part of the written area in a simple, easy-to-read format.

Include everyone in 20 mins

Traditional functional specification documents try to include the team: the developers, the designers, management, the client, and the Board.

Will your boss read the document? Can you be sure your client will read the document?

And if they do read the traditional written document, are you 100% sure that everyone understands it fully?

Take everyone through the application in 20 mins. Show them the interface right from the homepage and take them through the system.

1. Let people see what the finished system will look like before a single line of code is written

2. Let people point out how a particular page of function isn’t working how they first envisaged before the development team spend three weeks implementing it

Eliminate the surprises

Ensure that when you deliver the first version of your project that there are no surprises.

Remember, with a traditional Functional Specification the developers may interpret the written document differently from the client.

We eliminate the risk of delivering that doesn’t meet client expectations by showing them the user experience before a single singe of code is written we ensure that we significantly reduce the risk of delivering an unsuccessful project this way.

If you would like to know more about our User Interface Experience Specifications or how we can help you with your project call us on 0844 669 0878.