Avoid common mistakes that slow down projects and lead to frustration. Learn what not to do and how to fix these issues for better, faster results.
Vague descriptions force your team to guess what you want, leading to:
❌ Too Vague:
Title: Update Website
Description: The website needs some updates. Please make it better.
❌ Too Vague:
Title: Fix Bug
Description: Something is broken. Please fix it.
❌ Too Vague:
Title: Design Something
Description: We need a design for marketing.
✅ Be Specific:
Title: Update Homepage Hero Section with New Branding
Description: Replace the homepage hero section background image with attached hero-bg.jpg, update headline to "Transform Your Business with AI", and change CTA button color to brand blue (#3B82F6).
✅ Provide Details:
Title: Fix Contact Form Submission Error on Mobile
Description: The contact form on /contact page doesn't submit on mobile devices (iPhone Safari and Android Chrome). When users tap Submit, nothing happens. Started after Jan 10 update. See attached screenshot showing console error.
✅ Include Context:
Title: Design Social Media Graphics for Product Launch
Description: Create 4 social media graphics (Facebook, Instagram, Twitter, LinkedIn) announcing our new product launch on Feb 1. Include product image (attached), headline "Introducing ProductX", and CTA "Learn More". Use brand colors from attached guidelines.
Avoid these vague phrases:
Instead, be specific:
Without access, your team can't start work, causing:
❌ No Credentials Provided:
"Please update the homepage."
(No login information provided)
❌ Wrong Credentials:
Username: admin
Password: password123
(Credentials don't work)
❌ Incomplete Access:
Website URL provided but no admin login
Or admin login but no FTP access when needed
❌ 2FA Not Mentioned:
Credentials provided but 2FA enabled
Team can't access without 2FA codes
✅ Provide Complete Access:
Website Access:
URL: https://mysite.com/wp-admin
Username: admin@mysite.com
Password: [secure password]
2FA: Disabled for this accountHosting Access (if needed):
cPanel: https://mysite.com:2083
Username: cpanel_user
Password: [secure password]
✅ Test Credentials First:
✅ Create Temporary Access:
Before submitting request, verify:
✅ Admin URL provided
✅ Username provided
✅ Password provided (securely)
✅ Credentials tested and working
✅ Sufficient permissions granted
✅ 2FA disabled or codes provided
✅ Additional access provided if needed (FTP, hosting, etc.)
Unclear requirements lead to:
❌ Unclear:
"Add a form to the website."
Questions: Which page? What fields? Where should it go? What happens when submitted?
❌ Unclear:
"Make the site mobile-friendly."
Questions: Which pages? What specific issues? What devices to test?
❌ Unclear:
"Redesign the homepage."
Questions: What style? What sections? What content? Any examples?
✅ Clear Requirements:
"Add a contact form to the /contact page with fields: Name, Email, Phone, Message. Form should send to contact@mysite.com and display 'Thank you' message on submission. Place form below the contact information section."
✅ Specific Details:
"Fix mobile responsiveness on homepage, about page, and services page. Issues: Menu doesn't work on iPhone, images overflow on tablets, text too small on mobile. Test on iPhone 12 (Safari) and Samsung Galaxy (Chrome)."
✅ Complete Vision:
"Redesign homepage hero section with modern, minimalist style. Include: Large headline, subheadline, CTA button, background image. Reference: https://stripe.com (similar layout). Use brand colors from attached guidelines. See attached mockup for layout idea."
Include these details:
✅ What: Exactly what needs to be done
✅ Where: Which page/section/location
✅ How: Specific implementation details
✅ Why: Purpose or goal (helpful context)
✅ Examples: Reference sites or mockups
✅ Success Criteria: What defines completion
Lack of feedback causes:
❌ No Response:
❌ Delayed Feedback:
❌ Vague Feedback:
✅ Respond Promptly:
✅ Be Specific:
"Thanks for the design! Here are my revision requests:
- Change header background from blue to #3B82F6
- Increase body font size from 16px to 18px
- Add 20px padding around hero section
- Replace placeholder logo with attached logo.svg
Everything else looks perfect!"
✅ Approve When Ready:
Quick Acknowledgment:
"Thanks! I'll review this today and provide feedback by end of day."
Specific Revisions:
"Great work! Just two small changes:
- Make the CTA button larger (current: 14px, new: 16px)
- Change button color to brand blue (#3B82F6)
Then we're good to go!"
Clear Approval:
"Perfect! This is exactly what I wanted. Approved and ready to launch. Thank you!"
Out-of-scope requests cause:
❌ Mobile App Development:
❌ Backend Infrastructure:
❌ Content Creation:
❌ Media Production:
❌ Print Design:
✅ Web Development:
✅ Web Design:
✅ Digital Graphics:
✅ Check Scope First:
✅ Alternative Solutions:
✅ Approve at 90%:
✅ Batch Revision Feedback:
✅ Trust Your Team:
✅ Respond Promptly:
✅ Be Clear:
✅ Stay Engaged:
✅ Check Knowledge Base:
✅ Ask Your PM:
✅ Use Platform Features:
✅ Understand Turnaround Times:
✅ Plan Accordingly:
✅ Break Down Large Projects:
✅ Maintain a Backlog:
✅ Plan Monthly:
✅ Keep Queue Full:
| Mistake | Fix |
|---|---|
| Vague descriptions | Be specific and detailed |
| Missing credentials | Provide complete, tested access |
| Unclear requirements | Define all requirements clearly |
| No feedback | Respond within 24 hours |
| Out-of-scope work | Check scope before requesting |
| Over-revising | Approve at 90%, batch feedback |
| Poor communication | Respond promptly, be clear |
| Not using resources | Check KB, ask PM, use features |
| Unrealistic expectations | Understand timelines, plan ahead |
| Not planning | Maintain backlog, prepare ahead |
Q: What if I've already made these mistakes?
A: No problem! Just correct them going forward. Your team is here to help.
Q: Will mistakes affect my service?
A: No penalties, but avoiding mistakes leads to better, faster results.
Q: How do I know if my request is clear enough?
A: If someone unfamiliar with your project could understand it, it's clear enough.
Q: What if I don't have all the information?
A: Ask your PM for guidance or wait until you have complete information.
Q: Can I fix a request after submitting?
A: Yes, edit the request or add comments with additional information.
Q: What if I'm not sure if something is in scope?
A: Ask your PM before submitting. They'll clarify or suggest alternatives.
Q: How many revisions are too many?
A: If you're past 3-4 rounds, consider if you're over-revising. Approve and move forward.
Q: What if I need to change requirements mid-project?
A: Communicate changes immediately via comments. Major changes may need new request.
Contact support@thrivepix.com or message your project manager