Redesigning a Website Workflow

redesigning a website workflow

We’ve had the pleasure of working with JWC on a regular basis and they approached us with a big project – a complete overhaul of their website workflow. As we dug into the project, we found that several of their core processes were costing them unnecessary time and were inefficient. This often occurs with business sites that have evolved over time. A user experience or original website workflow doesn’t adapt to the changing needs of the business. Instead of proceeding with a reskin or a theme cleanup, we outlined a ground-up rebuild.

User Experience

The first part of the project was a complete redesign of the site. We were fortunate to be working with Nien Studios on the redesign. With Robert, we collaborated with JWC Environmental’s design team. The skills brought to bear during the wireframing and mockup phases set the tone for the whole build. We paid specific attention to the goals of the site. Then the design was built around achieving those goals. The end result leveraged their brand and delivered a modern and goal-oriented approach for the user.

Data Architecture

While design was underway, back-end development centered around clearly defining the data architecture. This activity was critical to streamlining business processes for managing the site. With the brain of the site built, it became much easier to create the functional components that presented those pieces to the user. These solid data structures mean we can adapt to future changes in the business. If we need a new website workflow with changing goals we won’t have to restructure the data again. We can design a new front-end experience to present the data in a way that meets those goals.

Localization Changes

One of the coolest features of the site came out of a desire to reduce the number of websites on the JWC Environmental network. We worked with WP Engine’s GeoIP capabilities to deliver region specific content in several areas of the site. What used to take several sites can now be accomplished with one.

A Revitalized Website Workflow

JWC Environmental was a great partner in the process. Their website is much more user friendly, filled with functionality, and designed with a purpose. The best part is that the theme we built for jwce.com is usable across JWC Environmental’s network of websites. As time has passed, we’ve made incremental updates to some sections. The solid data structure has kept those changes on the front-end of the site and costs manageable. We look forward to the next evolution of the site.

If your website workflow needs some TLC or your user experience isn’t up to snuff, reach out to us. A great place to start is with an audit so we can determine how deep the problems go.

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.

Flexbox - Modern CSS part 1

Flexbox – Modern CSS Part 1

About this Series In this series, we will explore one component of modern web development with CSS using practical examples as they might relate to a typical WordPress website. We will focus on these techniques in practice and provide resources to really level up your understanding of the topic. This first post focuses on flexbox.…
Read More
orange county wordpress meetup on gulp

Orange County WordPress Meetup: Gulp

Brandon Dove demos Gulp a Javascript task runner similar to Grunt but made for speed at the Orange County WordPress Meetup.
Read More
how-to-perform-a-website-audit_sidebar

Maximize your website's appeal and keep everything working for the best conversions.

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.