Problems Happen – And That’s Normal

Every website project has bumps in the road. Even big companies like Apple and Google face challenges when building websites. The difference between success and failure is how you handle these problems.

Think of it like renovating your shop. Sometimes you find unexpected issues behind the walls. The key is working together to solve them.

1. Timeline Delays

Your website takes longer than expected.

Why this happens:

• You needed more changes than originally planned
• Technical problems took time to solve
• You were busy and couldn’t review work quickly

2. Budget Changes

The project costs more than the original estimate.

Why this happens:

• You asked for extra features
• The original brief wasn’t detailed enough
• Unexpected technical challenges appeared

3. Communication Breakdowns

You and your developer aren’t understanding each other.

Why this happens:

• Different expectations weren’t discussed
• Technical language causes confusion
• Not enough regular check-ins

4. Quality Issues

The website doesn’t work as expected.

Why this happens:

• Requirements weren’t clear from the start
• Not enough testing was done
• Different devices show different results

Step 1: Stop and Think

Before you react, take a deep breath. Most problems have solutions.

Ask yourself:

• What exactly is wrong?
• How urgent is this?
• What would fix this?

Step 2: Talk, Don’t Email About Big Problems

Pick up the phone or meet in person. Big problems need real conversations.

What to say:

• I’m concerned about this specific issue
• Can you help me understand what happened?
• What are our options for fixing this?

Step 3: Focus on Solutions

Don’t spend too much time on blame. Focus on moving forward.

Good approach: The contact form isn’t working. What’s the quickest way to fix this?

Bad approach: You messed up the contact form. This is terrible.

When Your Website is Late

First, understand why

• Did you take long to give feedback?
• Were there technical problems?
• Did you ask for extra features?

Then find solutions

• Can some features launch later?
• What’s most important to have working first?
• How can you speed up the remaining work?

When Costs Go Up

Ask these questions:

• What specific work caused extra costs?
• How much will the total project cost now?
• Can we cut some features to save money?

Your options:

• Pay for the extra work
• Remove some features to stay on budget
• Phase the project (launch basic version first)

When Communication Breaks Down

Reset the relationship:

• Schedule a proper meeting
• Agree on how often you’ll check in
• Ask them to explain things in simple terms

Set clear expectations:

• How quickly should they respond to you?
• What’s the best way to contact them?
• Who makes the final decisions?

When Quality Isn’t Right

Document the problems:

• Take screenshots
• Write down what should happen vs. what actually happens
• Test on different devices

Work together on fixes:

• Agree on what “done” looks like
• Set a timeline for fixes
• Test each fix before moving on

Use These Phrases

• I need to understand our options
• What would you recommend we do?
• Can we find a solution that works for both of us?
• I’m concerned about this. Can we discuss it?

Avoid These Phrases

• This is completely wrong
• You don’t know what you’re doing
• I want my money back
• I’ll find someone else

Consider bringing in help when

• You can’t agree on what the problem is
• The developer stops responding
• You feel the project is completely off track
• Money disagreements can’t be resolved

Your options for getting help

• Ask another developer for a second opinion
• Contact trade associations for advice
• Use mediation services
• Seek legal advice for serious disputes

At the Start of Your Next Project

• Write down exactly what you want
• Agree on how problems will be handled
• Set up regular check-in meetings
• Discuss what happens if things go wrong

During the Project

• Respond to questions quickly
• Give feedback regularly
• Ask questions when you don’t understand
• Keep records of important decisions

Keep Good Records

• Save all emails and messages
• Write down what was agreed in meetings
• Keep copies of all contracts
• Document any problems and solutions

Know Your Rights

• You should get what was promised in writing
• Quality work should match industry standards
• You have the right to clear communication
• Serious problems should be fixed at no extra cost

Warning signs

• Developer disappears for weeks without explanation
• They ask for all money upfront before starting
• They won’t show you any work in progress
• They refuse to explain technical decisions
• They become angry when you ask questions

After Solving a Problem

• Document what was learned
• Update your project plan if needed
• Improve communication for the rest of the project
• Focus on the positive progress made

Remember

• Problems are temporary
• Good communication solves most issues
• Professional relationships can survive difficulties
• Your website will get finished with patience and teamwork

1. Problems are normal: every website project has challenges
2. Focus on solutions, not blame: work together to fix issues
3. Communicate clearly: use simple language and avoid accusatory phrases
4. Document everything: keep records of problems and solutions
5. Know when to get help: some problems need outside assistance
6. Prevent future problems: learn from current issues to avoid repeating them
7. Protect yourself: keep good records and know your rights
8. Stay professional: maintain good relationships even during difficulties