Building a Workflow That Works

Flowing water

One of the first things we communicate with a new client is what the workflow for their project is going to look like. We’ve even written a document that breaks down the general flow of a project and what they can expect from us and what we expect from them. We treat this as a living document. If we come up with a better way of communicating this information, we adapt the document to reflect that change. Our goal is to create a document that helps our clients understand our approach and expectations for the project. This documentation in turn helps us to refine our processes.

The Basic Workflow

One benefit is that we’ve now outlined our basic workflow. We flow from a kickoff meeting into the project. If there is a design phase for the project we’ll have a design meeting, then we’ll move into wireframes. We’ll proceed into mockups once wireframes are approved, and then finally into the front end development. Depending on the project, backend development may begin very early or it may come in along with the front end development for the site. Finally, we’ll move into the testing and refining period of the project. There is nothing out of the norm with our approach but by having it spelled out in detail, clients feel more comfortable knowing what to expect from the feedback cycle.


Beyond conveying the basic flow of the project, we are able to convey our expectations to the client. Simple things like communicating our normal hours of operation go a long way to empowering the client. Conveying more complex issues such as content creation and content entry being the responsibility of the client is also addressed. Practices that are industry standards may seem obvious to us, but may not be obvious to our clients. We don’t want our clients to have any surprises along the way.


The most important aspect of the workflow document is that it evolves over time. If we have a new service addition, it gets added to the document. When we change our hours of operation, they get updated. Where a specific process isn’t functioning, we can review the process and make changes to it in an attempt to improve the interaction. We believe strongly in collaborating with our clients and want to make sure that we have a tool for transparently communicating the details of the partnership. So far it’s been very successful for us and reduced confusion.

We’ve even adapted the idea to other processes in our organization. Even if we’re not sharing these with people outside of our organization, having good documentation makes discussion and refinement easy. If you need help defining your workflow we’re happy to consult with you about how to get started.

Written by the Team at Pixel Jar

We hope you got something useful out of that post. If you'd like to read more we have an active blog with topics across the spectrum of website development. If you're researching information for a project we'd love to talk to you about it.

intranet with big waves

An Intranet with Big Waves

We’ve recently completed development on a revised intranet site for The Innovation Institute. This site specifically delivers human resources features to the Institute’s network of almost twenty companies. Each company has slightly different guidelines and many of them operate autonomously. The project was challenging and it was really rewarding to see the final build. Repeat…
Read More
good website design in-browser

Good Website Design In-Browser

Welcome to the fourth installment of our five part series about custom approaches to good website design. In this post we’re talking about in-browser design. Suspending Formal Design In-Browser Design can be useful for projects where there is a built-in audience, where the lifespan of the site is short, or where the development timeline or…
Read More

How Can We Help You?

We want to build your next project.

Connect with Pixel Jar

Our Community

Subscribe to learn more about the goings on at Pixel Jar.
  • Note: Your email will be added to our CRM and be used to receive emails from Pixel Jar. You can unsubscribe at any time.

  • This field is for validation purposes and should be left unchanged.