Category: 2. Designing & building your website

  • Building and Maintaining Website Forms That Handle Sensitive Data

    Building and Maintaining Website Forms That Handle Sensitive Data

    Building and Maintaining Website Forms That Handle Sensitive Data
    Building and Maintaining Website Forms That Handle Sensitive Data
    0:00
    –:–

    Someone in your organisation needs a form added to your website. It might be for enquiries, applications, registrations, or internal processes. On the surface, it sounds like a straightforward web task, and it often gets treated that way. But the moment that form starts collecting sensitive information, it stops being “just a form”. It becomes a data processing system, and the risk profile changes.

    Once you’re collecting things like health information, identity documents, or anything that can meaningfully affect someone if it’s exposed, you’re into a very different category of work. That matters for the end client, it matters for the agency building it, and it matters for the suppliers and freelancers implementing it. If something goes wrong, it rarely lands solely on one party.

    Let’s look at what “sensitive” means in practice, and why the legal and security bar is higher than most people expect.

    Why the data type changes everything

    Special category data needs more protection because of the harm it could cause if it is mishandled or exposed. Under UK GDPR, organisations must identify a lawful basis for processing personal data (Article 6). If the data is special category, they also need a separate condition that specifically allows them to process that category of data (Article 9). In practice, that means the question is not just “can we collect this?”, but “are we allowed to collect this, and can we justify collecting it in this way?”

    This is also where a DPIA often comes in. A DPIA is a Data Protection Impact Assessment. It is a structured way of thinking through a processing activity before you implement it, so you can identify the risks to the individuals whose data you are collecting and decide what controls are proportionate. You do not do one because it feels bureaucratic. You do one because it forces the project to make the risk visible while there is still time to change the design.

    Are we allowed to collect this?
    Can we justify collecting it this way?

    That is not red tape for the sake of it. It is the practical recognition that, when the data could cause real harm if exposed, the bar for how you design, store, secure, and retain it should be higher than the bar for a contact form on a brochure site.

    This is also why reassurance alone does not close the loop. Even if everyone involved is acting in good faith, the moment the website stores sensitive data you have increased the attack surface and multiplied the places that data can persist. That is before you factor in backups, logs, email notifications, spam folders, or plugin-specific storage quirks.

    The shared risk between client, agency, and developer

    From a governance point of view, the client is usually the controller because the client decides why the data’s being collected and what it’s used for.

    Agencies, consultants, and suppliers often operate as processors when they build or host systems that process personal data on the client’s behalf, and that has practical implications for responsibilities, contracts, and how security decisions are made. The ICO’s guidance on controllers and processors is useful here because it explains how to think about the roles, and why it matters when something goes wrong.⁠⁠​

    Risk can become invisible when it becomes distributed.

    What I see happen in real projects is that the risk can become “invisible” because it’s distributed. The client assumes the agency will handle it because they’re the technical experts. The agency assumes the client will set the compliance direction because it’s their data. The developer assumes the plugin defaults are fine because they work for typical projects or perhaps they haven’t been included in relevant discussions. Nobody is acting irresponsibly as such, the system just drifts into a risky place through circumstance and blurred lines of responsibility.

    Start by minimising collection and retention

    If you want a practical starting point that almost always improves the situation, it’s this: collect less, and keep it for less time.

    Collecting less is the most powerful lever because the safest data is the data you never collect. If a form is collecting special category data, it’s worth challenging whether every field is truly necessary at that stage of the process. In many organisations, forms slowly accrue “useful” fields over time because it’s easy to add another question. That creates risk without anyone explicitly choosing it.

    Retention is where websites quietly become long-term liabilities. UK GDPR’s storage limitation principle is essentially the idea that personal data shouldn’t be kept for longer than necessary.⁠⁠ In a web context, the difference between “we’ll delete it later” and “it will definitely be deleted” comes down to whether deletion is engineered into the system, whether it’s tested, and whether someone is accountable for it.

    The safest data is the data you never collect.

    Don’t store sensitive data on the website if you can avoid it

    If you can design the system so the website doesn’t store the sensitive data at all, that’s usually the cleanest option. Other than not asking for the data in the first place of course!

    In an ideal world, submissions go directly into the organisation’s internal systems, or into a specialist provider built for handling that type of data, with the website acting as the collection interface rather than the storage layer. That reduces duplication and makes it far less likely that sensitive information ends up scattered across plugin tables, file systems, email inboxes, and server backups.

    I realise some organisations can’t support that pattern because their IT teams are trying to remove complexity and don’t have the capacity to build or expose endpoints. That’s a real constraint, and it’s one reason these projects can be tricky. But even when you can’t hit the ideal, it’s still useful because it gives you a direction of travel: reduce storage, reduce duplication, reduce persistence.

    If you do store it, deletion has to be designed and verified

    If temporary storage is unavoidable, the project needs to include a retention method that actually works in practice, not just on paper. This is particularly important on WordPress, because many form plugins don’t store everything in one obvious place. It’s easy to delete an “entry” and still leave uploaded documents on disk, or to purge a table while copies remain in email notifications, spam bins, logs, or backups.

    That’s why I’m cautious when a retention plan is described in vague terms like “we’ll delete submissions after 30 days”. Unless the team has confirmed exactly where the data is stored, and what “deletion” really removes in that specific setup.

    This is also the point where the conversation usually shifts from build to maintenance. If the form is collecting high-risk data, it can’t be treated as a one-off deliverable. It needs patching, monitoring, access reviews, and periodic checks that retention controls still function after plugin updates and configuration changes. This is where website management and maintenance stops being a “nice to have” service and becomes the thing that prevents the same problem reappearing in two years.

    Where Cyber Essentials fits in the conversation

    In sensitive-form projects, the security conversation often gets simplified into a question of standards. Cyber Essentials is one of the first things that gets referenced in the UK, because it is a recognised scheme and it maps to a set of common technical controls. The NCSC describes Cyber Essentials as a minimum standard aligned to five controls designed to help protect against the most common internet-based threats.

    It is also worth remembering the broader context. The UK government’s Cyber Security Breaches Survey 2025 reports that 43% of businesses and 30% of charities identified at least one cyber security breach or attack in the last 12 months. That is not a guarantee you will be breached, but it is a useful reminder that “we won’t be a target” is not something you can build a plan around when the data involved is sensitive.

    43% of businesses and 30% of charities identified at least one cyber security breach or attack in the last 12 months.

    The part that is easy to miss is that certification does not automatically mean the controls are sufficient for every processing scenario. The ICO explicitly notes you may have to go beyond Cyber Essentials depending on your processing activities, because it is only intended to provide a base set of controls and will not address the circumstances or risks posed by every processing operation.

    So, it can be part of a sensible security posture, but it does not replace the form-specific work: being deliberate about what data you collect, where it is stored, who can access it, how long it persists, and how those controls hold up after updates and staff changes.

    A litmus test that keeps everyone honest

    If you want one question that cuts through ambiguity, it’s this: if this exact dataset leaked, would everyone involved still be comfortable explaining the storage and retention choices to the people who submitted the form?

    If the answer is “I’m not sure”, that’s not a failure. It’s a sign you’ve found the real work, and it’s worth slowing down long enough to design the data handling properly before building anything.

    Want an outside perspective?

    If you are about to add or replace a form that collects anything sensitive, and you want a calm second pair of eyes on the practical risks, I’m happy to help. I spend a lot of time in the real-world edge cases where websites, plugins, hosting, and internal processes collide.

    I’m not a substitute for a data protection professional and I don’t provide legal advice, but I can help you stress-test the real-world implementation: what you are collecting, where it may be stored, and how retention is likely to work in practice.

    If that would be useful, feel free to get in touch. Sometimes a short review at the start prevents a painful clean-up later. Get in touch by calling me directly on 01903 527927 or via my contact page.

    Appendix: links mentioned

  • Should You Buy Multiple Domains for Local SEO?(updated)

    Should You Buy Multiple Domains for Local SEO?(updated)

    0:00
    –:–

    If you’re thinking about buying extra domains like “keyword + town” to rank in more places, you’re not daft. You’ve seen competitors doing it, and it kind of feels like a shortcut that should work, doesn’t it?

    In the past this is a tactic that had been shown to give results, although it also used to work much better than it does now, which is why unfortunately this idea doesn’t seem to be going away.

    However, in modern local SEO, buying more domains is rarely something that generates results. In fact, it often creates technical problems that make it harder to rank, harder to measure what’s working, and harder to improve your site without it turning into a complicated mess the more you add.

    A quick clarification (because “multiple domains” can mean two different things)

    When people talk about “multiple domains for local SEO”, they usually mean one of these:

    • Multiple domains, multiple websites (separate sites, often with similar pages)
    • Multiple domains redirecting to one main website (extra domains pointing to your primary domain)

    The first setup is where the real SEO and technical issues show up. The second is usually fine, but it is not an SEO growth strategy on its own, it’s more something to do if you have a bunch of related domains or domains previously used for the same business and you want to forward all those old links to your new site.

    Why people think this works (and why it usually doesn’t)

    Back in the day, keywords in domains carried more weight, and you could sometimes get traction from exact match domains. Google has moved on, and their guidance has been consistent about this for years.

    Google’s John Mueller has explicitly said that having keywords in a domain name is not going to help you rank for those keywords, and that you do not need to put keywords in the domain name.⁠⁠​

    So if your goal is local visibility, the domain name itself is very rarely the magic ingredient that you’re missing.

    The technical SEO problems multiple domains create (and why they become expensive later)

    Let’s be honest here. Most businesses don’t have the time to maintain one site properly, let alone three or more sites, so multi-domain setups tend to drift into the same predictable issues.

    1) You split authority and signals across domains

    Google treats each domain as its own website. That means links, engagement, and brand signals get scattered. Even if you are doing good work, you are diluting the effort and spreading it thinly, and that is the opposite of how SEO tends to compound.

    A good local SEO setup is usually one strong site that gets stronger over time, not several weaker sites competing with each other for your attention. One reason I think this became a thing back in the day was the attempt to crowd out the top search results with sites which were all owned by you, displacing the competition and driving them down onto page two. What’s the old joke? Where’s the best place to bury a corpse? Page 2 of Google.

    A good local SEO setup is usually one strong site that gets stronger over time

    2) You end up with near-duplicate pages, then indexing gets weird

    This is the big trap. When you have multiple domains, you almost always end up repeating service pages with light edits (because who has time to write genuinely unique content for each site?).

    People talk about “duplicate content penalties” like it is a dramatic punishment. The real issue is more frustrating: Google has to choose which version to index and show, and the versions can end up competing with each other. That can mean a lot of effort for surprisingly little return.

    3) Canonicals, redirects, and sitemaps become a minefield

    Multiple domains multiply the number of places technical SEO can go wrong. In the real world, I usually see issues like:

    • canonical tags pointing to the wrong domain or wrong URL
    • redirect chains (or inconsistent 301 rules)
    • bloated or inconsistent sitemaps
    • Search Console data split across properties, making diagnosis slower and more confusing

    This is the sort of stuff that does not look “broken” on the surface, but it quietly undermines performance.

    4) Tracking becomes unreliable (so you cannot make good decisions)

    If you care about leads, you need to be able to answer basic questions like “Which pages are generating enquiries?” and “Which locations are actually working?” Multiple domains often means tracking is fragmented, and it becomes harder to make changes with confidence in the data.

    What Google actually rewards for local SEO

    Local SEO is largely about helping Google understand:

    • what you do (relevance)
    • where you are, and who you serve (distance and service area signals)
    • whether you are clearly trusted and well-known (prominence)

    A big part of local visibility is your Google Business Profile. If your profile is weak or lacks continuity with the information on your website, it can hold a strong site back. If your profile is strong, it can sometimes carry a mediocre one. I’ve certainly seen this myself, where a new client has a website with poor content but which sees an immediate lift in traffic after the owner creates a business profile linking back to their site.

    Google themselves describe local ranking around relevance, distance, and prominence.⁠⁠​ Schema fits into local SEO as well, but it is worth being clear about what it does. Schema is not a magic “rank me higher” button. It supports clarity and consistency, and it can help search engines interpret your content properly (and in some cases support rich results), but it doesn’t replace good structure, good content, and a properly maintained profile.⁠⁠​

    Schema is not a magic “rank me higher” button

    The better approach: one site, clear structure, proper location pages

    If you want to target multiple towns or areas, you usually do not need multiple websites. You need one well-organised website that makes your coverage obvious and is technically clean.

    Step 1: Commit to one primary domain

    Pick a branded domain and make it your source of truth. It keeps authority, tracking, and maintenance simple, and it makes technical fixes much easier to do properly.

    Step 2: Create a clean location page structure (use fictional examples)

    Pick a pattern and stick to it. For example:

    • /areas/exampletown/
    • /areas/sampleville/
    • /areas/demovillage/

    Or service-first if that fits your site better:

    • /services/website-support/exampletown/
    • /services/technical-seo/sampleville/
    • /services/wordpress-maintenance/demovillage/

    Step 3: Make each location page genuinely useful (not spun)

    If the page is just “same text, different town name”, it is not going to help much.

    Instead, write it for a person in that area. Include a few real specifics so it earns its place, such as local trust signals, practical constraints, the kinds of questions people tend to ask, and a clear next step.

    What a good location page actually needs (so it pulls its weight)

    This is the bit most people get wrong. They create ten location pages, swap the town name in a few headings, and then wonder why nothing happens.

    A location page needs to feel like it was written for someone in that area, and it needs to give Google a clear, non-conflicting signal about what the page is for. If it’s thin, generic, or basically the same as five other pages on your site, you’re not building relevance. You’re building clutter.

    They create ten location pages, swap the town name in a few headings, and then wonder why nothing happens.

    A solid location page usually includes a handful of things that are boring, but effective:

    • Clear local description: what you do in that area, written normally
    • Local proof: a testimonial, a case study, or a real example
    • Practical detail: boundaries, response times, and what you do and don’t cover
    • Internal links: connect properly to your service pages and your “areas you cover” hub
    • Clean setup: unique titles and headings, and no canonical weirdness that makes pages compete

    If you do those consistently, your location pages stop being “SEO pages” and start being proper landing pages that win enquiries.

    Step 4: Keep the technical hygiene tight

    This is the bit that stops local pages leaking performance. When you have multiple location pages, pay attention to:

    • internal linking (avoid orphan pages)
    • titles and headings (avoid duplicates across pages)
    • canonicals (avoid mixed signals)
    • sitemap and indexation (avoid bloat and low-value URLs)

    Do that well and you give Google a clean structure to understand, and you make your own site easier to maintain and improve.

    What about buying extra domains and redirecting them?

    If you already own extra domains, redirecting them can be useful for brand protection or offline marketing. Just don’t expect the redirected domain name itself to give you a local ranking boost.

    Not sure if your setup is helping or hurting? Here’s what I can check quickly

    If you send me your main domain and a list of any extra domains you own, I can usually tell you pretty quickly whether you should consolidate, redirect, clean up canonicals, or fix indexing signals so your site is not fighting itself.

    👉 Book a call if you want a technical second opinion. No pressure. Just practical advice. You can reach me on 01903 527927 or via my contact page.

  • 10 Concerns When Hiring a WordPress Web Designer

    10 Concerns When Hiring a WordPress Web Designer

    Introduction

    Choosing the right WordPress web designer is an essential step toward creating a website that not only looks great but also functions smoothly and meets your business goals. Whether you’re building a new site from scratch or redesigning an existing one, it’s natural to have questions and concerns. Let’s explore the most common concerns you might experience when embarking upon this process.

    My name is Paul Edwards, I am a Web Consultant and WordPress Developer and I’ve been working with websites and businesses like yours since 2005.

    Cost, Experience, and Timeline

    1. Cost Concerns

    Why does hiring a professional WordPress web designer cost so much, and how can I be sure it’s worth the investment?

    Hiring a professional WordPress web designer ensures you get a high-quality, customized website that leverages the power, flexibility and scalability of the WordPress platform. The cost will likely reflect the designer’s length of experience and the number of times they have previously carried out theme customization, plugin integration, and optimising for performance and security. A well-designed WordPress site can significantly enhance your online presence, improve user experience, and offer better SEO performance. The ROI can be substantial through increased sales, better customer engagement, positive impact on brand reputation and lower average costs for site edits and improvements.

    2. Experience and Expertise

    How can I be sure that the WordPress designer understands and can execute my company’s vision?

    A professional will take the time to understand your business, industry, and specific needs. This might be called research and discovery or pre-project consulting. The result of discovery work should end with the presentation of a strategy or proposal for how to manage the project and clearly articulate how the project goals will be met. The strategy and proposal will be supported with real data acquired in the research phase.

    The designer will be able to clearly articulate the process ahead for you and provide references from previous happy clients. They will also provide mockups and prototypes to ensure their ideas align with your goals and seek sign-off before moving forward. You can read more about using a web consultant here.

    3. Timeline Issues

    What if the project takes longer than expected to complete?

    A professional web designer will provide a detailed project timeline, outlining each phase of the research, design development and testing processes. Regular updates and open communication help manage expectations and address potential delays promptly. By setting realistic timelines and keeping you informed, the designer can work efficiently to meet your deadlines and minimise the chances of overruns.

    Sometimes, a client will change a goal or brief part way through the project, and that’s OK. We are all allowed to change our minds and when that happens, the project will be halted and a new estimate and timeline provided for the new direction of travel. This allows expectations to be managed and both parties to keep on track.

    Any contract in place will clearly express what happens in case of project overrun, how this is handled practically and any potential financial implications. For example, client delays which prevent a deadline from being achieved may attract extra time costs at an agreed rate per day of delay. Being clear about this upfront allows both sides to measure the impact of decisions and changes in direction. The contract in tandem with the quote will clearly state if the project is fixed cost, or if overruns are billable. No professional will have a problem agreeing on these terms with you before proceeding.

    The Design Process: What to Expect

    Understanding the web design process can help alleviate concerns about timelines and quality. Typically, the process includes initial consultations, design drafts, development, testing, and revisions. Clear communication and defined milestones ensure the project stays on track and any issues are addressed promptly.

    Quality, Communication, and Compatibility

    4. Quality and Reliability

    How can I trust that the WordPress designer will deliver high-quality work and remain professional throughout the project?

    Reputable WordPress designers build their careers on delivering high-quality work and maintaining professionalism. You can verify their reliability by checking client testimonials, case studies, and reviews. A well-established designer will also provide a contract outlining the scope of work, timelines, quality standards, and evidence of their professional indemnity and/or public liability insurance.

    A good designer will provide an unhurried initial consultation and answer any questions that you may have which will give you a sense of their commitment to quality and professionalism. Trust your gut, do you feel that the designer has done this all before and this is routine for them, or does it feel like they are feeling their way through the early days of working in the industry? Don’t be scared to ask, and expect a full and honest response.

    5. Communication and Collaboration

    What if there are communication issues, and the designer doesn’t understand my needs or feedback?

    Effective communication is crucial for a successful WordPress design project. Professional designers use clear, structured communication channels, such as regular meetings, progress reports, and project management tools, to ensure ongoing collaboration. They prioritize understanding your needs through detailed briefs and questionnaires and encourage feedback at every stage. This iterative process ensures that your input is valued and incorporated into the design.

    Established web designers will seek constant feedback and request signoff at significant stages before proceeding to ensure that misunderstandings either don’t happen or are rectified before they impact the project. Probability dictates that very rarely an issue may arise, look to reviews to see how the designer has handled any conflict and ensure that if you proceed, your contract includes a section explaining how to manage a potential breakdown in the working relationship.

    6. Compatibility

    How can I ensure that the WordPress designer’s style and approach align with my company’s brand?

    Before starting the project, a professional WordPress designer will conduct a discovery phase, where they learn about your company’s values, target audience, and branding guidelines. Discussion with your designer will also help you assess their style and see if it matches your brand aesthetic. Open discussions about your brand’s identity and providing examples of websites you admire can further align the designer’s approach with your vision.

    Although a designer’s website will likely have told you a lot about them and their approach before you contact them, it will become quickly apparent what their approach is when talking, if it doesn’t ask about their values and what they enjoy working on.

    Hiring a WordPress Designer: The Process

    1. Consultation: The first step is an initial consultation to discuss your project’s needs, goals, and budget. This helps the designer understand your vision and establish a strong foundation for the project.
    2. Proposal and Agreement: After understanding your requirements, the designer will provide a detailed proposal outlining the project scope, timeline, and cost. Once agreed upon, a formal contract is signed.
    3. Design and Development: This phase involves creating design drafts and wireframes, followed by the development of the website. You’ll have the opportunity to review and provide feedback at each stage.
    4. Testing and Revisions: Before launching, the site undergoes thorough testing to ensure functionality and performance. Your feedback is crucial during this stage to finalize any necessary revisions.
    5. Launch and Post-Launch Support: Once approved, the website is launched. The designer will also offer post-launch support and maintenance to ensure your site remains up-to-date and secure.

    Technical Skills, Scope, and Support

    7. Past Experiences

    I’ve had negative experiences with previous designers. How can I be sure this won’t happen again?

    To mitigate the risk of repeating past negative experiences, look for WordPress designers with strong reputations and positive client feedback. Request references and speak directly with previous clients about their experiences. Clear contracts and setting detailed expectations upfront can prevent misunderstandings. Opt for a designer who is transparent about their process, timelines, and deliverables, and who prioritizes building a trustworthy relationship.

    8. Technical Skills

    How do I know if the WordPress designer has the technical skills needed for my project?

    Assessing a WordPress designer’s technical skills involves reviewing their portfolio and looking for examples of work similar to your project. Ask specific questions about their experience with WordPress themes, plugins, and customizations. Certifications, ongoing education, and participation in WordPress communities can also indicate a commitment to maintaining technical proficiency. Additionally, many designers provide case studies that detail their problem-solving and technical capabilities.

    I encourage you to seek evidence of continuing professional development in core and supporting subjects and technologies. CPD shows that your designer is engaged in actively learning and developing and will likely take the same approach with your web design project.

    9. Scope Creep

    What if the project scope changes and leads to increased costs and extended timelines?

    To manage scope changes, a professional WordPress designer will define a clear project scope and deliverables in the initial contract. Any additional requests or changes are handled through a formal change order process, which includes revised cost estimates and timelines. Regular check-ins and setting priorities can help keep the project on track. Transparent communication and a flexible but structured approach ensure that any scope changes are managed efficiently without compromising the project’s overall success.

    10. Post-Launch Support

    Will there be support and maintenance available after the WordPress website is launched?

    WordPress professionals often offer post-launch support and maintenance packages. These services can include regular updates, security checks, plugin management, and troubleshooting to ensure your website remains functional and up-to-date. Discussing and including post-launch support in your initial agreement can provide peace of mind. Reliable designers may also offer training for your team to manage basic site updates and provide access to documentation to facilitate ongoing site management.

    Conclusion

    Hiring a WordPress web designer is a valuable investment that can significantly boost your business’s online presence. By addressing these common concerns you can feel more confident in your decision and ensure a successful collaboration with your chosen designer. If you have any more questions or are ready to start your project, feel free to contact us!

  • Web Design Terminology Explained: A Comprehensive Glossary

    Web Design Terminology Explained: A Comprehensive Glossary

    Unfortunately in the world of web design it is true that both web designers and businesses can use terms and phrases which either mean different things to each party or which are simply not understood by the clients.

    My name is Paul Edwards, I am a web consultant and frontend developer based in Worthing, West Sussex. Today I answer the question “What are the frequently misunderstand niche terms used by a web designer?”

    I have provided this glossary with the aim that it may help you understand the wonderful language of web designers. Should you not find the term that you are looking for or would like to discuss a particular communication in a bit more depth you can call me on 0193 527927 and I will be happy to help.

    A – B – C – D – E – F – G – H – I – J – K – L – M – N – O – P – Q – R – S – T –U – V – W – X – Y – Z

    A

    Above/Below the fold

    The fold is a term which originated in the newspaper and print industry. The fold was the part of the paper that got folded. And Above the fold refers to the copy which was visible above the folded/hidden portion of the paper. Any content not visible was referred to as Below the fold.

    These terms have moved from the print industry into the web industry where the terms now refer to content on a page visible above the bottom of the screen being used and the content not seen without scrolling the page. In the below image the orange line represents the bottom of the screen or what would be the fold in the middle of a newspaper.

    Screenshot of Wikipedia page showing definition of 'Above the fold'

    Accessibility

    Accessibility refers to making website content easy to consume by as many people as possible including those who may have special requirements due to physical or mental impairments or conditions which differ how content may be perceived.

    Examples of improving accessibility include high contrast and low contrast colour schemes. Formatting to make it easy for those using screen readers to navigate and listen to page content. There is a law in the UK governing accessibility and you can read more about accessibility at the UK Gov website or at the W3C introduction to accessibility.

    Analytics

    Data/statistics about your website, how it is viewed, devices used to view the site and demographic information. Analytics data is important in helping decide strategy, what content is successful/unsucessful and in identifying  changing habits of users. Analytics are often viewed in some kind of software interface such as Google Analytics. Analytics are often tied to advertising campaigns, social media content, and can be used to track traffic generated by those campaigns and content.

    API

    A set of rules that allows different software entities to communicate with each other, facilitating interactions between different software applications.

    Back to Top

    B

    Backend

    Although this is a gross simplification, when web designers refer to the frontend they refer to what is seen. When they refer to the backend they refer to what is unseen. Backend developers tend to be directly involved at a server level and working on the software and databases that power the website which displays the frontend. Frontenders design and style the visible content of a website and get involved in building themes and working on front end features and functions. Typical backend languages can include (but are not limited to) Java, PHP, Ruby on Rails, Python, and .Net.

    Backlink

    A link to your website or content from another website.

    Backup

    A copy of your website database and/or files. There are lots of different types of backups, some created by plugins in WordPress and others created manually via a PHP admin interface, ftp or software installers like Installatron or Softaculous (on cpanel). Backups should be run before and after any significant change so that your website can be restored should something go wrong and your site or part of your site is lost or defaced. Ideally backups are carried out at frequent intervals as part of a website maintenance plan.

    Useful resources:

    10 simple steps to bulletproof wordpress backups

    Do you do these 10 things during website maintenance?

    Why you need a website maintenance plan for your WordPress website

    How often should you backup your website?

    Bounce

    A bounce describes the act of a website visitor arriving at a page and then leaving without interacting with any other links on the page. A high bounce rate can be indicitive of problems with your content and/or usability of your website.

    Bounce rate is a key statistic which is measured by analytics packages such as Google Analytics. Google provide more information about bounce rate here.

    Breadcrumb

    A text device that shows the location of the page you are currently viewing in the site hierarchy.Breadcrumbs are text links often seperated by arrows or some kind of visual device which indicates what level of a website hierarchy the page you are viewing is at. Here is an example:

    Homepage>Main Category>Sub Category>Product

    Normaly the link farthest to the right is the page you would be looking at with each link to the left being one higher level in the hierarchy of the website.

    Back to Top

    C

    Cache

    Websites often have software caching programmes and servers often have both caching hardware and software. Caches temporarily store information for rapid retreival to cut down on the time taken to deliver that information. Caches dramatically speed up the delivery of website and that caching can occur at multiple levels from server, website and the users browser.

    Typical WordPress caching plugins in use:

    WP Optimize (I use this a lot)

    WP Rocket

    WP Super Cache (built by the people that make WordPress)

    W3 Total Cache

    SG Optimiser (requires Siteground hosting)

    CDN (Content Delivery Network)

    A system of distributed servers that deliver pages and other web content to a user based on the geographic locations of the user, the origin of the webpage, and a content delivery server.

    CMS (Content Management System)

    CMS stands for Content Management System, a software platform that allows easy management of website content. Often ‘drag and drop’ in nature, CMS’s are easy for non-web professionals to use without specialist knowledge.

    WordPress is one of the most popular content management systems on the planet and it is responsible for delivering about a third of all websites in existence. Originally starting out as a blogging platform, WordPress is one of the easiest CMS for clients to use as it has an easy to navigate dashboard and content creation interface.  Because WordPress is quick to setup and easy to work on it tends to be popular with small to medium enterprises that have limited marketing budgets. Find out more about WordPress here.

    Drupal is often called a content management system but to be honest it is more of a framework for building bespoke content management systems. Drupal can literally do anything but can have a steep learning curve although that is improving. Very suitable for large data sets or large numbers of users.

    There are many other CMS’s available but in my opinion these are the main two worth your consideration and which have the best community support and a wide number of agencies and freelancers available to support you.

    Content

    The words, images, branding and files included on a web page for consumption by visitors.

    Content marketing

    This term relates to the creation and sharing of content online in order to build awareness of a brand. Content marketing can include the following activities:

    • Building and optmising landing pages
    • Guest blogging
    • A/B testing
    • Searching for broken links in articles and offering your own content as replacement
    • Social media posts
    • Webinars
    • Paid advertising
    • Live video
    • Mapping content to pain points

    Copyright-free images

    Images which are provided for use by others although the copyright for the image may remain with the original owner. Copyright-free images are often free to use but may require some kind of credit for the image displayed.

    I really enjoy using a website called Pexels.com as they have some really high quality images which are all free to use.

    CSS

    Your web designer may refer to stylesheets or CSS. CSS or Cascading Style Sheets contain the code which applies visual styling to the content on a web page. CSS uses classes and id’s which are added to HTML to style how the content in the HTML appears. An example of a simple bit of CSS:

    .text-large {

    font-size: 30px;

    }

    The above code will make any text which has the class ‘text-large’ applied to it 30 pixels high.

    The HTML end applied to a paragraph of text would look like this:

    <p class=”text-large”>Content text goes here</p>

    Back to Top

    D

    Deliverable

    A deliverable is an item which is ‘delivered’ to a client as part of a contract. Typical deliverables may include:

    • Wireframes
    • Static visuals
    • Responsive mockups viewable in a browser
    • Strategy documents
    • Statistics
    • Branding guide
    • Logo pack

    Digital format

    Often a term used to describe the fact that an image has been taken, created or converted to a digital format via a digital process. Digital cameras produce digital format images. A pdf document of terms and conditions would be a digital format document.

    Typical digital image types are:

    • GIF
    • JPG or JPEG
    • PNG
    • BMP
    • TIFF
    • RAW
    • SVG

    Typical digital file types are:

    • PDF
    • XML
    • HTML
    • RTF
    • TXT
    • DOC
    • XLS

    Typical digital video file types:

    • AVI
    • FLV
    • WMV
    • MOV
    • MP4

    Discovery (discovery phase)

    Discovery is one of the first stages of a new website project with a client. The discovery phase is scaled to the needs of the project but broadly, includes:

    • Research
    • Analysis
    • Technical audits
    • Competitor research
    • Strategy
    • User journeys
    • Customer research
    • Site mapping
    • Content planning

    Downloading

    The act of transferring a file from a website or online source to a local device such as a computer or phone. Files can be downloaded from a website by clicking on a link, right clicking on an image or file or by downloading directly from a server using FTP and an FTP client.

    Drupal

    Drupal is an opensource content management system which is used to build, manage and maintain websites.

    Back to Top

    F

    Favicon

    The small image displayed in a browser tab which represents/identifies what website is being viewed in that tab. Favicons can also be used and displayed as shortcuts.

    The favicon for this website can be seen in the tab you have open now. It should look something like this:

    Frontend

    Frontend refers to the visible part of a website and the files and technology that contributes towards showing that website.
    A frontend developer gets involved in coding templates and working on stylesheets and functions using languages such as HTML, CSS, JAVA and JQuery and PHP.

    FTP

    FTP stands for File Transfer Protocol and is the most common way of transfering files to and from remote devices such as servers and computers.

    FTP Client

    FTP clients are software designed to help users connect their computer to a server by providing an easy to use interface that stores login credentials for accounts and creates a visual bridge between local storage and online storage. Often a client will provide syncing tools and more. You should be aware that you need to use SFTP if you require secure transfer of files.

    Commonly used FTP clients available are:

    Back to Top

    H

    Heavy (that page is heavy)

    A webpage can be described as heavy if it is bulky and takes up a higher than expected amount of server space. An image can also be described as heavy if it has not been optimised for viewing online and is many megabytes in size.

    The average web pages size in 2019 is 3.29MB which is in my opinion huge. I try to ensure any page is below 1MB and I would describe any page over 1MB as heavy.

    In terms of images on a page, I try to have any regular image below 50k and any banner image below 150kb. Anthing above 200kb is ‘heavy’ using my frame of reference.

    Avoiding heavy pages and images is really important not only so that visitors have a page load quickly in their browsers or on their mobile phones but also because page speed is now a factor in where a site ranks in search engine results. As a rule, pages with a smaller overal size load faster and rank higher.

    Hit

    A hit is a request recieved by a server to display an item on a webpage such as an image. One page may generate many hits but still only be classed as one visit.

    HTML

    Hypertext markup language. It is the language used to present content in a webpage. For more information about HTML please have a look at this Wikipedia entry.

    Back to Top

    L

    Landing page

    A landing page is a page on a website which is designed to be presented to people who may be clicking on an advert elsewhere or be part of a sales funnel. A landing page is normally crafted to have minimal distraction and links away from it to encourage a visitor to carry out a particular task.

    Landing pages can be hand crafted in code or by using plugins in WordPress such as:

    Most plugins that create landing pages are premium in nature and this means that you will have to pay a subscription or license fee to use them.

    Lazy Loading

    A design pattern commonly used in web development that defers the loading of non-critical resources at page load time, instead loading these assets as needed when they enter the viewport (visible part of the web page).

    Back to Top

    M

    Meta tags

    Meta tags describe something about a webpage such as what it is about, when it was created, and what keywords might be relevant. Commonly used meta tags are:

    • Title tag
      The title of your page displayed to visitors and search engines. The visible number of charactors in Google is between 55 and 64.
    • Meta descritpion
      The summary of a web page. The visible number of characters in Google is up to 160.
    • Alt tag
      Text which explains what an image is so that screen readers can understand and those that view sites as text only know what content should be in that place. Search engines also use Alt tags as they cannot ‘see’ images.
    • Robots meta tag
      Tells search engines and other crawlers whether it should index or follow a page.

    Microinteractions

    Small, single-purpose interactions that enhance the user experience in an app or website, such as the reaction of a button when clicked or a loading animation.

    Mobile First

    A method of designing a website for mobile phones first, and then adding extra layers of styling and function for other devices with larger screens later.

    Mockup

    A mockup can sometimes be a static visualisation of how a website is proposed to look. Sometimes a mockup can be interactive and created using specialist software tools or even be a live (but limited) website viewable in a browser.

    Back to Top

    N

    NDA

    An NDA is an abbreviation of Non-Disclosure Agreement. An NDA is normally an agreement that dictates what and when both parties in a contract can and cannot disclose certain information about the agreement to third parties.

    Often when an agency sub-contracts work to a freelancer they use an NDA to restrict the freelancer from telling third-parties about the project unless there is a genuine need to do so such as employing another third-party to complete a task. This means that freelancers often cannot use work they completed under NDA in their portfolios.

    NDA’s often include some kind of penalty that may be imposed should and NDA be ‘broken’ by either side.

    Back to Top

    P

    PDF

    Portable document format created by Adobe Corporation. PDF’s have commonly been used for creating small file size documents with limited editing ability or some kind of password enabled security feature. PDF’s have been used online for downloadable documents for many years but their popularity has perhaps started to dwindle in recent years.

    Pen testing

    An abbreviation of Penetration Testing. Ethical hackers can try to penetrate your website and/or server with the intention of uncovering security flaws so that they can be removed/fixed.

    Plugin

    The blogging platform WordPress which has morphed over time into a Content Management system allows the use of additional small bits of software called plugins to extend functionality. Other CMS’s like Drupal also use similar software extensions but call them Modules.

    Prod (short for production)

    Prod refers to the live website available to the public. Developers and designers often repeat the mantra “dont edit prod”. Instead of making edits to a production site, we can do those edits on a development or staging website. Staging sites are copies of the live site which can be worked on and then the changes can be ‘sent live’ once they are approved.

    Progressive Web App (PWA)

    A type of application software delivered through the web, built using common web technologies including HTML, CSS, and JavaScript, intended to work on any platform that uses a standards-compliant browser.

    Back to Top

    R

    Responsive

    The ability of a web page to change size and shape to fit the screen size and orientation of the device being used to view it. An analogy is often used of pouring water into different shape containers. The water adopts the shape of the vessel into which it is poured. Responsive web design attempts to achieve the same with a web page being viewed on screens of varying sizes and proportions.

    Back to Top

    S

    Scope Creep

    Scope creep describes when additional requirements are added into the project that were not in the project brief. If not handled efficiently and appropriately, scope creep can cause a project to exceed budget and deadline.

    Proper pre-project discovery and discussion with the client to inform the brief can help avoid scope creep. Where despite best efforts it does occur, it should be addressed early and where appropriate schedule the additional works to be completed after the main contract or cancel the existing contract and start a new one with the new features included with amendments made to timeline and budget.

    SEO

    Search engine optimisation. A method of altering the structure and content of web pages to improve their chances of being found higher up in the search engine results pages for a chosen set of keywords relevant to those pages. SEO is based upon a combination of information made public by search engines such as Google and experimentation. If anyone gaurantees to put you on page one of Google, be sceptical. There are no gaurantees.

    SSL

    Secure socket layer. A security method for creating an encrypted link between a web server and a browser. You will often hear web designers talking about SSL certificates which you can purchase to create a secure connection to your website. SSL certificates are essential if you recieve or send any important, personal or sensitive information via your website.

    Once only found on websites taking payments online, SSL certificates are fast becoming the norm for all new websites as visitors have more trust in sites that use them. Google has also revealed that sites with SSL certificates may get a small bump in the search engine listings.

    I recommend that all websites use an SSL certificate. Some common SSL certificate vendors are:

    Staging (edited)

    A live but restricted access copy of your website on which changes and edits can be made and tested prior to pushing those changes to your live (production) site. Cheap hosting packages dont often come with staging sites but these are easily created on a subdomain or alternatively if you purchase a more fully featured hosting package you may find that a staging site function comes built into the management dashboard.

    Static layout

    A static layout is a mockup which uses a fixed-width page size which does not respond/change to screen size. Static layouts are reducing in practicallity since the rise the use of mobile devices because they do not show the responsive nature of content. It is possible however to create multiple static visuals for each likely screen size and type that will be in use. Personally I find this takes longer than to create a basic responsive mockup in the browser for clients to view. As such, I dont generate static layouts for projects anymore.

    Back to Top

    U

    UX

    Short for User Experience. If you want to learn about user experience I suggest you have a look at the website of Paul Boag, a User Experience Consultant who has worked for many large and well known brands. Paul has lots of articles and guides on his site and frequently runs courses about user experience related topics.

    Back to Top

    W

    Website Maintenance

    The ongoing work that is required to keep a website current. Modern websites that run on a CMS such as WordPress require ongoing updates to the core software and the additional extensions (called plugins) to fix security flaws and bugs that are identified by users and developers. I recommend monthly website maintenance to keep your website resilient to hackers and bug/error-free.

    White label

    When a freelancer, contractor or agency carry out work for another party and remain invisible to the client. The work is then presented as work completed by the person employing the sub-contractor. Many small agencies sub-contract work to freelancers on a white-lable basis and in most of these instances, the sub-contractor is not allowed to show that work in portfolios. Such activity is often goverend by an NDA (non-disclosure agreement).

    White space

    The empty space around content on a web page. White space is a good thing! White space helps bring focus to elements on the page and can be used to help create visual hierarchy and a sense of priority.

    Widget

    An editable and reusable block of content on a WordPress website which shows up in ‘sidebars’. Sidebars can be added to areas of a page such as footers, headers etc. giving the site owner the ability to easily edit information that can be found in more than one place. Sidebards do not have to be displayed in the ‘side’ of a page but can be added anywhere by the web designer.

    Wireframe

    A very quick and often rough line drawing of a web page and its content areas to help clients and themes visualise how a webpage should look.
    Often those that build web pages are given a set of wireframes and/or static visuals to base their designs upon.

    WordPress

    WordPress is a content management system. Approximately 30% of the world’s websites are built and managed using WordPress.

    Back to Top

  • Rethinking Your Website Portfolio: Is It Helping or Hurting Your Business?

    Rethinking Your Website Portfolio: Is It Helping or Hurting Your Business?

    Blog Audio: Read/listen time: 8 minutes

    In a departure from the regular ‘how-to’ kind of blog posts that I write, I thought that I would (for a change) cover something about website content.

    1. Do you use your website to generate sales or enquiries?
    2. Do you have a portfolio on your website?

    Today we discuss:

    Why might you generate better enquiries WITHOUT a portfolio on your website?

    A bit of a provocative question? Perhaps, but bear with me for a moment.

    Let’s clear this up now. In a vast number of cases, possibly yours too, portfolios are a good thing. However, for businesses like mine (and possibly yours) which work with a wide variety of client types and produce a wide variety of output types a portfolio can be directly harmful to both the number and type of enquiries generated by the website.

    Portfolios tend to generate more of the same

    You may be thinking “excellent” and if that is the case, then don’t let me waste any more of your time. However, if you or your business have multiple client types rather than a highly targeted narrow client base your portfolio might be losing you enquiries or attracting clients which don’t match your future goals.

    If you have largely worked for small businesses and sole traders but want to move towards a different client base made up of say, legal professionals, your portfolio may be slowing you down or potentially even stopping you from reaching your goals.

    Essentially your portfolio may keep you continuing down a path that you want to deviate from. It develops a life of its own filtering out opportunities that you may have wanted to take.

    ‘Cliques’ but not of the conversion kind

    People tend to be drawn to those that are similar to them. Similar traits make people feel more comfortable with each other as it reduces risk, reduces the chance of surprises and also simply takes less effort to communicate.

    If you were looking for a contractor for work, would you pick someone with a history of working for people just like you or a contractor that appeared to do an unrelated kind of work?

    The work you display in a portfolio will likely be what you consider your best work but is it the kind of work you want to generate more of? Human nature is going to deliver you more of the same so quite honestly if you have a wide client base you may be better off not displaying a portfolio at all.

    How to turn a lack of portfolio into a hook for the right kind of client

    People are suspicious animals. If you don’t display a portfolio there can be the immediate assumption that:

    • you are inexperienced
    • you are likely bad at your job
    • you have ‘just started out’
    • all of the above

    The reality is though that there are many reasons why you may not display a portfolio:

    • You white label work for other agencies and designers and it would be damaging to your relationships to reveal you did the work
    • You signed agreements or NDA (non-disclosure agreements) that prohibit you from revealing the work you did
    • You don’t want your company to be linked to the client for negative publicity reasons
    • You may not have done the visible design work for the project
    • The projects may no longer be live to ‘show’
    • You don’t frequently edit your site and are unlikely to keep your portfolio up to date

    The key is to ensure that you carry out some objection handling so that answer any worries the potential client may have before they fully form.

    If you white label for others and cant reveal work, say so. If you work under NDA, say so.

    Communicate in your content that you have a portfolio of work and that you will be happy to send any prospective client a list of ‘recent’ work that you have carried out on the basis that they will be discreet. To do this I normally agree with my agency clients on a shortlist of works that I can show people on a one-to-one basis but which I wouldn’t widely publish online so as to not cause any embarrassment. Most agencies who employ a freelancer to carry out works don’t tell the client that they are doing this.

    Respond to enquiries in a way that makes you the solution

    The reality is that potfolios are lazy. Portfolios are impersonal and put the burden on the client to carry out work to assess you.

    If a prospect contacts you and asks why you don’t have a portfolio, or if they contact you because you said you could show them some work, do so. Make sure however that you do your homework to find out what kind of business the prospect runs. When you have a firm idea of what the project is going to be, simply return a tailored list of previous projects that match that client’s industry or sector.

    Such an approach really does work because:

    • it is personal
    • it is tailored
    • it starts a conversation offline

    If you don’t have a perfect match in your history of completed works to show the client, try and look for a common denominator between what the prospect is telling you about and another project you have completed. The work may have been for a different type of client, or in a different field but if it has a common issue or goal then you can talk about how you solved that issue.

    Often a prospect will dismiss portfolio work based on industry or client type which actually would, with closer examination, show that you can solve their problem efficiently.

    Why don’t I use a portfolio?

    For every enquiry I do not get because I don’t have a visible portfolio I get an enquiry that I wouldn’t have got with a wide unfocused portfolio. Allowing potential clients to view your online portfolio means that you aren’t there to explain your involvement fully. It is very easy for a client to misunderstand your role in a project, even if you include explanations alongside any links and images. The client may not know that you built the project to another person’s design, or that you only got involved on a particular component of the project. You will always convert more leads to sales if you are the one talking to the client about the project, explaining how you added value and how you can do the same for the prospect.

    When I respond to a lead I respond with a positive tailored list of prior work which resonates with that client and the kind of work they are looking to complete. I really do believe that responding to a client in that way opens up early communication and helps you see if you are a good fit personality-wise.

    Most jobs are won because a client thinks that you will complement them well in terms of skills, that they get on with you and that they trust you. The portfolio becomes less and less important the longer your offline conversation continues.

    I firmly believe that I have lost more work from having a portfolio than I have lost enquiries from not having one. For me, the lack of a portfolio is an opportunity.

    Are portfolios bad?

    No of course not, when carefully focused and curated they can be a huge benefit but do be open to the fact that a portfolio is not always appropriate or helping your business get to its destination. For many of us, a visual portfolio does not allow us to effectively showcase how we can help our clients. That comes from engaging and having a focused discussion offline.

    The assisted portfolio ( a compromise )

    For many, the thought of not having a portfolio is unbearable. The joy of having a website is that you and I can use whatever approach works for us. If you arent comfortable with abandoning a portfolio entirely there are many compromises that you can make to try and get the best out of the content you do already have online.

    You could:

    • Use a portfolio page that allows clients to filter your projects by type, function or industry
    • Have one detailed project deep dive and encourage visitors to contact you to learn about other works you have completed
    • Explain your methods and then apply those methods to a hypothetical project to show your approach
    • Use video content of yourself explaining why you don’t have projects on your portfolio page and encourage a conversation to take place
    • Have a form on your portfolio page that allows visitors to contact you in order to receive a tailored list of projects you have completed that relate to their industry or project goals.

    If you want to talk about this in more depth feel free to get in touch. I’m always happy to discuss ways of helping your business reach its goals. Contact me directly on 01903 527927. Thanks for your time.

  • Harmony in Design: Five Ways to a Happier and Productive Web Designer

    Harmony in Design: Five Ways to a Happier and Productive Web Designer

    Blog Audio: Read/listen time: 15 minutes

     

    My name is Paul Edwards, I am a Web Consultant and Frontend Developer and I’ve been working in the web industry since 2005. Every day somewhere in the web industry projects fail, clients get unhappy and web designers get mistreated. So, lets have a look at 5 ways you can keep your web designer happy (and productive).

    Introduction

    While it is anecdotally reported that an unhappy workforce is a productive workforce this is most definitely not the case when you are working in creative industries.

    The joy with working with creatives is that they genuinely want to do the best for you. They are heavily invested in providing a product or service for you that not only helps you reach and surpass your goals but because their future income depends upon your happiness.

    Creatives tend to use their recent work as evidence for gaining new work. This shared goal sets you up for a situation that is geared from day one to be focused upon your project’s success.

    So, why then, if all parties want to succeed do so many web design projects fail to meet their potential? Why do so many business/creative relationships flounder and fail?

    Sometimes poor matching of a client to creative can contribute towards a breakdown in the relationship. Sometimes management by committee or scope creep can cause irreconcilable issues.

    So, with the happiness of your chosen creative established as a priority in helping you achieve your goals, let’s take a look at the top ways that you can keep your web designer on-side. Or conversely, if you wish to look at the negative, this will also explain how to alienate and stress your creative to breaking point.

    1. Pay. On. Time.

    Despite the fact that your chosen creative is selling their skills and/or the reaching of a specific goal, the relationship you have built is so very important.

    More than in some industries, creatives are often very personally invested in their work. Whilst being personally invested in a project is in many ways a very positive thing and should not diminish the level of service you receive from a creative worker sometimes the creative process can be derailed.

    Nothing derails a creative like not being paid on time. If you respect the team you have chosen to work with and you want then to respect you, please pay them on time.

    If you fail to pay your creative on time you are directly expressing your lack of respect for them. As much as creativity is a process or system and not magic, nothing stifles creativity as much as feeling as though their work and time isn’t respected. Clients that respect their freelancers will find that more often than not they will get better service, prompter service and that the person being employed will go the extra mile for them.

    Being a freelancer is a financially precarious job at times and if you look after your chosen web designer you will reap the rewards of that. Also, let’s not forget that if you don’t pay promptly you may find that you not only lose the goodwill of that person but that shortly after the conclusion of your project you may find that the person you didn’t pay promptly will not want to work for you again, so who is going to support your website in the future?

    2. Provide a single point of contact with a decision-maker

    I have been freelancing since 2005 and in that time I have found that where a project has run into issues there have been a few common causes. One of the most significant reasons for a project stalling or spiralling out of control from scope creep is when the project is being ‘managed by committee’.

    Freelancers and agencies alike will fall over themselves to tell you stories about this situation and more often than not, they will go a little something like this:

    The web designer is initially contacted by one person who discusses the job, provides a project brief and asks the designer for a quote for carrying out the required works. At this point we are at the point of maximum potential, the designer is fired up and excited for the potential of a new challenge and the client is happy to have found someone that they get on with.

    The quote is agreed and the project start date comes around and the designer eagerly puts some questions to the client and gets some rapid feedback. Mockups get worked on and signed off by the same person who as originally contacted the designer who dutifully produces an initial concept site which the client has a look at.

    Things go a little quite. The normal pace of response has changed and the designer feels a bit confused so contacts the client asking for feedback and gets a response a little like this:

    “Thanks for the work you carried out on the site, I’ve run it past (insert name of person or persons here) and they don’t like (insert arbitrary point here that has no impact upon the effectiveness of the page in reaching its goals)”

    Suddenly you realise that the person you have been talking to all along isn’t the decision-maker or lacks the confidence or skills to make a decision on their own without some form of validation from another person or a committee. Your project is now doomed.

    Doomed may be a bit of an exaggeration but the project has certainly hit a major obstacle that will require rapid and firm intervention to correct and to keep the project on track.

    Management by committee encourages the following:

    • causes every decision to take longer be a significant margin
    • increase the chance of having to make multiple changes to the same ‘thing’ often
    • makes every decision subjective based upon personal tastes rather than the performance against an agreed goal
    • makes it difficult to get sign-off on a project as any personal disagreements in the committee cause cyclical arguing
    • almost guarantees that someone at the client company will be unhappy with whatever solution is finally implemented because they were overruled and they didn’t like that solution

    Management by committee guarantees unhappiness missed targets and goals not fulfilled. It can very negatively impact relationships and often leads to a company or designer deciding not to maintain the relationship past the final payment being made.

    So how do you avoid management by committee?

    Both sides are responsible for this. A designer can point out before starting a contract that a single point of contact with a decision-maker is a requirement of the contract. Secondly, the client can work out its internal politics and procurement procedures before contacting a web designer.

    If you find that the longer you work with someone the more thier prices go up, you may be trying to manage them by committee and they are taxing you for being difficult to work with.

    Adherence to the above will make for a more successful project and a happier client/designer relationship.

    3. Keep to one round of snagging

    Snagging is a term that is used to describe the process of finding and raising for resolution, errors on the website.

    I give my clients access to a full version of their new website prior to it going live to allow them to ensure that there are no errors that have crept in either copied and pasted from their own copy or that may have been introduced by myself.

    While it is very important to carry out snagging not only to squash any errors that have been found it also gives a client an opportunity to make any changes to copy that may be required to match the time and date of release.

    When snagging goes bad

    In itself snagging isn’t a problem at all, it is actually a really important part of the project and it ultimately leads to the finalisation of the project and that magical moment of sign off, payment and putting the project live.

    An exciting time, so why can it be bad?

    Snagging can go bad when it isn’t confined to a single round of edits. Most often this is caused by a lack of thorough examination by the client and errors keep being added to the list drip by drip. This elongates the process and gives the effect of multiple rounds of snagging. Not only does this take considerably more time, it’s not likely to have been included in your original quotation for the work. This then makes the designer unhappy and causes project delays.

    If you combine this failure with management by committee you can create a never-ending cycle of edits, updates and changes which will ultimately lead to someone saying ‘no’. Or enforcing some kind of cut off or severing of the changes from the contract leading to additional costs.

    Although reasonable, additional costs then cause negative feelings with the client and can sour the relationship.

    Remember, a website is organic, changes can be made at any time and very minor errors and content changes are not always a reason not to progress with sending a site live. Websites can be updated at any time.

    4. Be timely in providing content and images

    It may have been written into the contract between the client and the web designer that all written content and images would be provided by the client to the designer in a timely manner.

    Although it is possible to build a website using placeholder text and placeholder images this is far from ideal and if you have employed the services of a solid web designer they will refuse to do this.

    Why? because if you want pages which are designed to work well, designed to be easy to digest and which improve the chance of conversions a web designer will need to design the page to the content.

    It is surprising to me that still, some people think that web designers build pretty boxes to put content into. They don’t, or at least they shouldn’t.

    To allow your web designer to do a good job they need your content first. Before they start work. If you don’t provide content in a timely fashion you start to introduce delays to the project. If you are delaying by a considerable period you may find that you start to trigger additional charges, pausing of the contract (meaning changes to the projected ‘go live’ date or in worse case scenarios, cancellation of the contract.

    Snatching defeat from the jaws of success

    Remember that we discussed that web designers future work and success is dependent upon doing a good job for you? If you don’t provide your designer with what they need to deliver on the agreed goals of the project, you are setting them up to fail in their task. The sad reality is that if they fail in their task, you fail in yours and as the last completed job by that designer, you affect their ability to attract that next job.

    A web designer’s success is so tightly aligned with yours that if you don’t give them what they need they will get frustrated and cranky because they really do want to help you reach your goals. It is more than that though. Delivering content on time will allow the momentum the project has gathered to be retained and harnessed. Pauses in projects lose this momentum, people forget what they were doing and it takes time to get back into a project after it has been shelved for a while.

    5. Don’t ask them to make the logo bigger

    OK, this last point is both something to have a laugh about but to also take seriously. ‘Making the logo bigger’ is something that people in the web industry laugh about. A lot. They also talk about it with despair, disbelief and confusion. The reasons for this are many and I hope this short explanation will help you understand why unless your designer has done something silly or damaging to your brand, you shouldn’t ask them to “make the logo bigger”.

    So why shouldn’t you make your logo bigger?

    The answer to this question is in the majority of cases an answer that a client really doesn’t want to hear. So, here we go. Customers don’t care who you are…

    There, I said it. In the majority of situations, a visitor is attempting to complete some kind of task efficiently, purchase something or gain some kind of knowledge. Have a super large logo on the page does the following things:

    • Pushes all content down the page and potentially past ‘the fold’. This reduces the visibility of content and reduces the chances of visitors engaging with the website and then going on to purchase something or complete some kind of call to action.
    • Competes for attention over and above the content on the page. Suggesting that your company is more important than the visitor. The visitor and the task they are trying to complete should be a bigger priority than ramming your branding down their throat.
    • Implies stupidity on the part of the visitor. They found your company in the search results, listen to an advert or read about you somewhere. Then they either typed in your website address (URL) or clicked on the link which let’s be honest, likely is the name of your company. There is no need to let the visitor know yet again where they are. It’s kind of patronising

    If you feel that you really should have a huge logo on a page, why not write down the names of the companies you most admire, direct competitors in your industry. Go to their website and have a look at the size of their logo and branding. The likelihood is that these companies have done the research, made the mistakes, studied analytics and come to the conclusion to minimise branding for a very good reason. I see no reason not to copy them.

    Let’s not forget the biggest reason (in the context of this blog posts title) for not making your logo bigger.

    Your chosen web designer has made the logo the size that it is for good reason. The size of your logo has not been decided randomly on the spur of the moment, it has been worked out to ensure that it balances well with your page content, that it is obvious and readable without interfering or dragging visitors eyes away from more important things like calls to action.

    The reason that your logo shouldn’t be made bigger is that then you are overstepping the boundaries of your part in the relationship. You are the client, they are the designer. They are trained, knowledgeable and practised in optimising page layouts to help you reach your goals. If you impose such changes on your designer you ignore their experience, their qualifications and all the good reasons that they may struggle sometimes to explain to you. You become the designer and you reduce them to being an assembly line. This doesn’t mean that you can’t make suggestions or discuss goals or problems. Talking about these things is really important to your designer, but please let your designer do what they are best at, helping you succeed.

    If you really insist, your designer will likely carry out your wishes. After all, they do want to get paid, but you may find them less willing to work with you in the future.

    So there we are. 2,524 words about how to keep your web designer happy and productive. If you would like a bit more help, feel free to call me on 01903 527927 and I would be happy to help.