Digital Marketing

Potential WebDev Project Glitches To Watch Out For

Submitted by Sam Moore on Thu, 02/25/2021 - 11:00
Image
Potential WebDev Project Glitches To Watch Out For

There are inherent technical minefields in every site dev project, but you may also have to deal with industry- or company-specific difficulties. These may include (but alas, are not limited to): 

  • Wonky Web browsers – It’s nearly impossible to create a site that will appear consistent across all of them  

  • Previous web developers, third-party IT people or uncooperative domain name registrars who’ve lost their clients to you, and spitefully cause a difficult transition 

  • Clients who believe the website you built on a CMS comes with free lifetime CMS training or telephone support from you. Boundaries (made concrete in the work agreement) are your friends. 

  • Clients whose staff, tapped to be their ongoing web maintenance people, are not the least bit tech-savvy. 

  • Clients who want you to build them a blog, but don’t want to resource someone to write anything for it. You need to make them aware of this ongoing need. 

  • Clients who don’t supply content on time…or at all; then don’t turn around draft reviews in time, but still want the website launched on schedule. 

Though we hope it doesn’t happen this way, all these issues and more are ones you must be prepared to deal with. Be very clear about your policy on these types of issues before the project begins. 

 

Maintenance & Backups – What WebDev Projects Really Look Like, Part 12

Submitted by Sam Moore on Thu, 02/18/2021 - 15:23
Image
Maintenance & Backups – What WebDev Projects Really Look Like

Tie up loose ends by ensuring that your good work will be properly maintained by the client (or your firm, or a contracted IT vendor, as the case may be).

Maintenance & Optimization 

  • If the client discovers that part of the site isn’t working, you need to fix it as quickly as possible. Original planning and budgeting needs to provide for this possibility, as well as for some amount of ongoing feature tweaks. 
  • One important (yet often overlooked) developer duty is to provide the functionality for a continual feedback loop with your client’s internal back-end users. Be prepared to answer questions such as, “I want to post a video, how do we do that?”
  • Consult Website Pulse's best practices to establish your own.

Back-End Management 

  • Another critical functionality is allowing new site owners to see all their content and make any necessary changes. 
  • This should be planned for when choosing the site CMS, according to the particular needs of the client, and the idiosyncrasies of its staff.
  • Try to anticipate these needs when creating training documentation, but don’t view questions outside of that coverage as annoyances. View them as learning situations for creation of the next site documentation, and as opportunities to provide a higher level of billable service.

Launch – What WebDev Projects Really Look Like, Part 11

Submitted by Sam Moore on Thu, 02/11/2021 - 16:43
Image
Webdev project

Once you’re ready to publicly launch the new site, be sure that beforehand, you’ve communicated to clients that, by their nature, websites are never “finished.” Remind them that this is a good thing: It makes a site more sustainable because it grows with their organization; and changes are usually less costly than print and broadcast.

The whole point of a website is that it’s not static, but a living entity. Again, emphasize the positive: Fresh content is bait for web spiders to crawl their sites, potentially bumping their rankings.

Now is the time to pay attention to the myriad tiny development details that will leave the best client impression.

Then it’s the Marketing department’s turn to have done their thing:

  • scheduling live or online launch events to tout the new Web presence
  • generating and distributing press releases (and posting them on the site's newsroom)
  • finding creative ways to tie in the site launch to timely current events

Though launch parties are always fun, they’re not only costly, they’re also bad form in the era of COVID, so use your imagination in creating fresh new approaches to launch announcements.

Testing, Round 2 – What WebDev Projects Really Look Like, Part 10

Submitted by Sam Moore on Thu, 02/04/2021 - 18:19
Image
Web Dev Testing Round 2

The Final Countdown
Your initial site go-live will be a “soft launch,” known only to those working on the project. First-round testing was for internal users to give the site a first run-through. But now, developers have seen the site too many times, and fresh eyes are needed. 

Unleash the Gremlins!
Second-round testing is done by those who might actually use the site “in the wild.” You want to unleash the gremlins before the general public has access. As military generals have always known: “No battle plan survives contact with the enemy.” People will find ways to break stuff. Let them do it before it really matters. This is the last stress test before the paying client sees it, and—more importantly—sees potential customers use it.

How To Do It
If you haven't run usability testing before, or you have but found it to be a vague process without actionable outcomes, you need a firm process in place. There are many places to find established processes, but one we recommend is Just In Mind. Just over a year ago, they published their Complete Guide to User Testing, with a dozen chapters of in-depth suggestions to address and set up all facets of usability testing. 

Training – What WebDev Projects Really Look Like, Part 8

Submitted by Sam Moore on Thu, 01/21/2021 - 13:53
Image
WebDev Training

With the site now live in its first complete iteration, it’s time to provide training to whoever’s job it is to update and maintain the site.

Documentation!
When handing the site over to the client’s IT department and content creators/editors, you need to provide documentation on how to perform necessary tasks. Match your options to deliver documentation to their strengths:

  • In person
  • Written
  • Videos/Recorded webinars
  • Powerpoint with screen shots – Standalone or attached to the back end of the site itself, prompted through pop-ups or icons.

The important part is that the guidance system you design be flexible. As always, put the user first in designing this.

  • What do internal users like?
  • Get comfortable with the idea that you may need to come in to revise it later.
  • One proven method of client training is the creation of a “Mentoring Model:” Train one client staff member who is good at training to teach the rest. In the best of cases, this can leverage the positive efficiencies of “hive mind.”

Testing & Going Live – What WebDev Projects Really Look Like, Part 7

Submitted by Sam Moore on Thu, 01/14/2021 - 13:48
Image
WebDev testing and going live

Having moved through the initial creative and production processes, now’s the time to test your work in the real world.

Testing – Round 1

  • Often, testing is only done by site owners, but end users should be put in front of the site, too, before it’s considered launch-ready.
  • Behavioral testing is a huge part of this practice: “If I click this, that should happen.”
  • Behavior-driven Web development is becoming the norm, through practices such as BEHAT. This is an open source Behavior-Driven Development framework for PHP. It’s a tool to support you in delivering software that matters, through continuous communication, deliberate discovery and test-automation. It’s essentially a series of “if-then” scenarios.

Review and Going Live

  • Only after your draft site is put through its paces against these tests should you allow the client to review it.
  • Either make requested revisions or explain to the client why the site should remain as is, then take the site live.

Coding & Marketing – What WebDev Projects Really Look Like, Part 6

Submitted by Sam Moore on Thu, 01/07/2021 - 13:46
Image
coding and marketing

Now you’re ready to tackle the backend coding that brings creative concepts to life. Coders must be mindful of the ways our work can help or hinder our marketing team members’ efforts. Always, this must be driven by the foundation of empathy for the user.

Tech and Usability Design & Coding
We need to make sure we can afford users the pathways they need. We must allow for anything they may need to revise: Typos, number of units ordered, etc. on eCommerce sites; save your work and start over, etc. on other types of interfaces.

Functionality Coding
Sometimes functionality drives the interface, but to the extent that we have control over how things work, we need to make sure that if users press the wrong button, they get feedback. Concise but gentle and understandable guidance is key to a successful user experience.

Marketing & SEO

  • How much do content editors need to know about keywords and the organization's search strategy?
  • Do they need to learn to create content that's in line with the marketing department's priorities?
  • If so, who will provide that guidance: a brand strategist, a guidebook?
  • Will there be a content approval process? Who will be responsible for that?

Graphic & UX Design – What WebDev Projects Really Look Like, Part 5

Submitted by Sam Moore on Thu, 12/31/2020 - 13:41
Image
WebDev Projects

The tenets of good user design fill at least a dozen books, and there will be more. This discipline grows in importance as retail moves more and more online. The learning curve was already picking up speed, but since the rise of the coronavirus and COVID-19, that speed has grown exponentially. We must grow with it, if we are to keep ahead of the very real needs of site users.

  • Graphic design is critical to every item seen by the site visitor, from the overall page template, fonts and color scheme to the look of buttons and other repeating elements. The person responsible for this should have a good balance of experience and knowledge in both 2D design and how that applies to an interactive, virtual experience.
  • User Experience (UX) design applies to everything from micro-interactions to the whole customer success journey. You test it by walking through the actual process a site visitor must go through. Then ask yourself: How hard was it to do what the fictional user wanted to do? How many hoops do you have to jump through? Could any of them be eliminated or made simpler? Do systems collaborate with each other smoothly?

Quoting & Planning – What WebDev Projects Really Look Like, Part 2

Submitted by Sam Moore on Thu, 12/10/2020 - 15:08
Image
Quote and Planning

Quoting & Planning – What WebDev Projects Really Look Like, Part 2
After you've gotten through the Discovery process to find out what your objectives should really be for a webdev project, next steps include:

Quote Submission

  • Your "quote" should actually be more of an estimate. We're all familiar with the concept of "scope creep" and—as with any act of creation—it rarely ends up being exactly what we anticipate. Allow yourself flexibility to compensate for this next point:
  • Allocate enough time and money for concepting and ideating about UX and testing, and reworking things according to what you find out during testing.
  • With any quote, you are setting client expectations. Write it with the thought in mind that you will need to stick to whatever promises you express or imply, so leave room to over-deliver.
  • Check out Muffin Group's great web design suggestions and quotation templates to figure out the best way to price your services.

Planning

  • If you're going to put the project in front of end users and act on feedback (and hopefully you are), you need to plan for the time and money to do this. All sustainable webdev projects are iterative.

This takes us up to the start of creative production work, which we'll cover in our next post.

Ready To Start – What WebDev Projects Really Look Like, Part 1

Submitted by Sam Moore on Thu, 12/03/2020 - 15:03
Image
Ready to Start Webdv

A Place to Start

There are any number of ways to start a web development project, but all contain the following basic functions. They tend to occur in pretty much the same order, though there can be some back-and-forth between stages during the development process.

In this and the next few posts, we'll offer our suggestions on how to break down the process into something relatively replicable. This makes it so much easier to plan and cost each webdev project.

Discovery This is where you gather the requirements of your project.

  • What, exactly, are you trying to build?
  • What do you want it to do?
  • How does it fit into your business?
  • Know thine client: If their content creators and editors are not tech-oriented, you need to know that from the beginning. It's hard to bolt on helpful functionality at project's end.

If you're comfortable with the concept of mind-mapping a challenge, there are some excellent examples at Mindmeister.com. Even if you've never done a mind map before, this site is like a large handholding exercise in the process.

Mindmeister will walk you, step by step, through the creation of your own mind map for each potential webdev project. It will take you from beginning to end of the discovery process, right up to the point when you're ready to pitch the project with a cost estimate.