Now that we have all of the details for your project, it’s time to get to work!
Project Management
We’ll manage your project from kick off to launch in our shared project Slack channel.
Internally, we also use our own Asana project to manage and communicate, so if things are quiet initially, know we are working behind the scenes.
Our Asana project also syncs to the Slack list in the project channel, so you’ll be able to see the tasks we’ve added and their status.
To keep things organized for our team, we generally create tasks for the following items. This also helps keep the conversation in one place.
- Project Management We use this task to communicate any general questions or the overall project status.
- Theme, header/footer, home page This task is what we use to work through the initial theme styles for the site, global header and footer, and the home page.
We spend the most time on this task to ensure things are dialed in before we start using elements on other pages so that we can build the rest of the site as efficiently as possible.
- Individual tasks for each page, template, or significant functionalities We’ll create tasks for each unique item based on the specs of your project.
- Create training guide/videos As we approach the end of development, we’ll prepare any site specific training guides or videos. We also document our dev notes so that any custom functionality or styles are noted for the future.
- Technical SEO Before launch, we want to ensure that any technical SEO details that are missing are in place as well as collect any redirects that might be needed for launch.
- Launch As we prepare for launch and take the site live, we’ll use this task to track those details.
Review and Feedback
As we move through each task above, we use a few status labels in Slack to indicate what is needed.
- Not Started This task is in our queue. No action is needed from you, but if anything has changed or you need to update us on something, feel free to comment on these items.
- In Progress We’re actively working on this. If you are also making changes to the development site, please use caution for areas that have this status as we may overwrite each other’s changes.
- Needs Approval Once our dev team has completed a task and it’s passed through our internal quality assurance review, we’ll move the task to Needs Approval in Slack and provide you with an update (we’ll tag you to ensure you get notified). Please reply within 3 business days with:
- Feedback or any changes that you need
- Approval that this task is complete (we’ll move it to the Complete status)
- Waiting/Valerian Blocked If we have started a task, but are missing assets, have run into issues that require your feedback, or need clarification, we will move the task to this status and tag you with what we need to move this forward. Please reply as soon as possible to keep the project running on time, ideally within 3 business days.
We understand that it will sometimes take longer than 3 business days when you’re waiting to receive something from the client. Getting back to us ASAP is appreciated.
How to give feedback
When we have marked a task as Needs Approval we’re looking for confirmation that:
- The item matches the provided design
- The item is responsive
- Functionality for the item works as intended.
If you catch any issues, please provide us with a Loom or screenshot with details and we’ll put the item back In Progress for development and submit it for approval again once we’ve made adjustments.
Change Requests
We get it, priorities change or the client changes their mind on something even after the design is submitted to us. Sometimes we can accommodate this easily within the current scope for the project, but sometimes it requires a bit of adjustment. Here’s how we handle change requests:
- If we haven’t started development and the design is not significantly different or includes functionality that isn’t wildly different than we initially scoped, we can likely accommodate within the current project scope.
- If we’ve already made significant development progress and/or the design or functionality changes drastically, we’ll need to scope the new changes and they won’t be included in the current project scope.
We can either do a flat rate add-on or bill hourly, depending on what’s best for you!
Let us know if the project Slack channel, and we can provide the next steps.