Project Specification. What is It and What Should It Contain?

What is a project specification?

Product design specification

  • appearance of the designed product,
  • number and type of the subpages (views),
  • information on the users or personas,
  • accuracy of the wireframes and prototypes,
  • information architecture,
  • visual expectations,
  • color preferences,
  • preferences regarding the photos, icons, and illustrations,
  • expectations resulting from the client’s corporate identity,
  • individual responsive versions.

Technical specification

  • expected functions of the system (e.g., CMS),
  • SEO parameters,
  • page load time,
  • project creation and implementation schedule,
  • needs of the responsive versions,
  • issues related to the constant technical maintenance of the website within the appropriate standard.

Requirement vs specification

Example

  • The form should be visible near the menu.
  • It should contain the first name and email fields, as well as the checkboxes confirming marketing consents.
  • After registering an email, a confirmation message in the form of a pop-up window should appear.
  • The form should be based on the color schemes of the company’s brand book.
  • The form should be synchronized with a newsletter system (e.g., Mailchimp).
  • The number of subscribers should be visible in the CMS panel.
  • The newsletter-related emails shouldn’t be flagged as spam.

Benefits of having a specification

What to do when the client doesn’t have a project specification ready?

Specification vs the MVP idea

Specification may evolve

Project specification — the summary

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store