Associative Trails / about

Intranet application development

We develop and maintain intranet applications for clients based in the UK.

We can help out during all the stages of intranet application development - from strategy, requirements capture, paper/html prototyping, specification, information architecture and usability; to server and client side development, SQL Server, Oracle or open source databases, accessibility, web standards, hosting and technical deployment.

An intranet application development project will include some or all of the following steps:

01

Kickoff

Initial discussions about the goals of your application, who the intended audience is, etc. From our base in Kent, the high-speed rail link gets us to anywhere close to London in double-quick time.

02

Proposal

We write a proposal document, sketching out general ideas for the intranet application and estimating costs and timescales.

Hand-drawn sketch of design ideas: a central page wireframe with arrows from sketches of the content it could hold, such as tweets, maps, photo galleries, video and a timeline.
Sketches of ideas for intranet application development
Hand-drawn sketch of a content model: official sources on one side and social sources on the other, drawn as icons, feeding by arrows into an admin interface and a published page.
Sketches of ideas for intranet application development
03

Contract

We sign a contract (between client and developer) to ensure all parties know their responsibilities and what is expected of them.

We often like to use a secure extranet to improve communications during the project and will provide a project programme setting out key stages and deliverables.

Screenshot of a project plan: a Gantt chart of weekly bars for each task from contract to launch, with ticks against completed tasks and milestone dates.
Project programme for intranet application development
04

Prototype

A prototype is a quick and efficient way of working out the key templates and important workflows of the intranet application.

Depending on the project requirements and budget, a static HTML prototype will allow us to explore a handful of key pages (e.g. home page, listing page, item page, search results, etc.) and lay them out exactly how they will appear in the final application. This enables good quality feedback on visual design, content hierarchy, layout for different devices (responsive design), etc. which can then be fed back into the design process.

Screenshot of an HTML prototype of an intranet home page: a video and news stories with photographs in columns, and a weather panel and noticeboard down the right.
HTML Prototype for intranet application development
Screenshot of an HTML prototype of a staff directory: an alphabet bar and search filters above a grid of portraits with names, roles and contact details.
HTML Prototype for intranet application development
Screenshot of an HTML prototype of a project page: a building photograph and project facts, a description above a grid of photographs, and a column of team members.
HTML Prototype for intranet application development
Screenshot of an HTML prototype of a member's profile form: personal and contact details, privacy checkboxes, and a table of their photographs with captions.
HTML Prototype for intranet application development

Sometimes, a project's programme or budget may mean we also produce a paper protoype - this allows us to consider a larger volume of sample screens and explore workflows more fully.

Wireframe of a form step for validating uploaded member data: a table of members with invalid entries outlined in red, beside a column of design notes.
Paper prototype for intranet application development
Wireframe of a form step for assigning members to categories: a list of members with arrow buttons moving them into category lists, beside design notes.
Paper prototype for intranet application development
05

Written specification

If the project would benefit, we will also provide a written functional specification document.

06

Development

Once the prototype and functional specification are signed off, we retreat to our Kent-based lair to develop the intranet application. We provide regular progress updates during this stage.

Screenshot of a weekly project progress summary: completed, ongoing and upcoming tasks in three columns with who owns each, and a notes box below.
Project progress report for intranet application development
07

Testing

When it is ready, we distribute links and security access to the intranet application to key client stakeholders for testing.

08

Launch

When everyone is happy with it, we launch the intranet web application.

Interested?

If you would like to discuss the development of your intranet application with us, please do not hesitate to get in touch.

Get in touch