Introduction.
This started as an email to a new friend that is trying to help churches set up websites. The email grew large enough that I thought it might make a blog post.
Common problems
Three common problems I have fallen into more than once when volunteering my time to build websites for friends or non-profits are getting stuck in the design cycle, managing ongoing maintenance requirements, and confusion over account ownership.
Below I will discuss each problem in more detail and the following section I recommend things that have helped me be more effective when helping people and organizations.
Getting stuck in the design cycle
Professional designers are amazing. As much as they are artistic wizards they are professional decision-makers. People not used to making design choices tend to get lost down the rabbit hole.
One way this manifests itself is when trying to decide on a webpage layout, constant logo iterations, and discussions about font or color scheme. People tend not to know, and they get stuck.
Getting stuck can be frustrating when volunteering your time. You end up spending more time than you budgeted for on a volunteer project.
Paid projects at least have the built-in consolation that you are at least being compensated for your time. Admittedly that doesn’t always salve the pain when you feel like you are wasting precious minutes of your life.
Ongoing maintenance requirements
You did it!! You made a website and the stakeholders don’t hate it. Go you!
Soon after ‘completion’, the emails start to roll in “Can you update just one thing? Could you add a button here real quick…. When you get a chance….. No hurry.
Hey, the site you built is down…. Can you fix it? We want to set up Outlook, can you add these DNS records.”
If you don’t transition the responsibility of managing the web property and set up appropriate boundaries you are unintentionally setting the expectation that you will be around to fix, update, patch, and create in the future.
If you are helping someone for free, you likely want to be helpful. However, if you don’t want to sign up for a lifetime of free support then you should make a plan to avoid it.
Confusion over account ownership
Before I knew better, I would set up all accounts for services under my company email. When customers transitioned away they would inevitably hit me up for help accessing service accounts.
Even when someone is not paying you, there is a common decency requirement to help someone who is suffering the consequences of your poor decision-making within reason.
So…..
A recommended strategy for a quick build, easy transition, and not have maintenance cost.
Define Project scope
Be super clear about what you will do and where that help ends.
Discuss and define who will write the content, who will create the logo, and who will pick the color scheme, font, and layout.
Example desinition(s)
“I will build your product a landing page based on a template that you pick out and buy from Themeforest. “
“I will install WordPress for you and set up your domain using your credit card, Cloudflare account, and email address.”
I recommend starting with the sitemap and the content first. Start by asking what do you need and what are you trying to say.
This makes it easier to find the right design.
One way to avoid getting stuck in the design loop is to find an existing theme or template that they like. This step can cut down on tons of decisions.
I recommend putting the onus on them to pick a design that they like from a marketplace like https://themeforest.net/
Once you have page content, layout, logo, color scheme, and a site map of the pages you are ready to make a draft.
Have a clear path, and let everyone know where you are going.
“If You Fail to Plan, You Are Planning to Fail” — Benjamin Franklin
Be clear about what the process will look like. This will benefit you and the stakeholders.
To avoid confusion over asset ownership, plan out what services and assets you are going to need. Do you need a domain, a Wix account, a theme purchase, a Cloudflare account,S3, etc.?
If so, set up those accounts with the client’s information or have them set up a new email address for all of the accounts that need to be set up.
Plan, Build, Launch, (Iterate), Transition.
I recommend that you front-load the work of creating the content, finding a design, and drafting a sitemap.
Moreover, It should be established before the project begins who will take on the responsibility after launch. It will be important that you as the developer understand the capabilities of the person who will take over the project so that you don’t build something unmaintainable.
For example, a simple static site hosted on S3 is fine for someone familiar with those technologies. However, that project would be a nightmare to update for someone who has never edited HTML before.
Give solutions not options.
If you are doing something for free for someone who doesn’t know how to do it themselves, you should feel confident in your recommendations.
When someone asks you what to do, give them an answer. Say definitively this is what you need if you believe it. Otherwise, you are introducing confusion and indecision.
Conclusion
If you like me enjoy helping people get on the web then I wish you the best of luck. I think these boundaries help prevent a fun and kind activity from turning into a life-draining chore for all stakeholders.
Recommendations
For email use Google Apps for business.
E-commerce use https://www.shopify.com/
If someone asks you where they should build a website my go-to is https://www.wix.com/
If it’s WordPress these are good options.
Leave a Reply