Our Partnership Begins Here.
Once the contract is signed and the deposit is issued, we’ll send you a spreadsheet detailing the various materials we need and accounts we require access to in order to get started. You can share this sheet easily with your collaborators and enlist their help tracking down assets. During this time, you’ll also be introduced to the project team and point-person/producer, Lena.
We invest a lot of time into our kickoff meeting – this is our chance to get to know you and understand your vision, aspirations and goals. Equal parts Q&A, therapy and work-session, this meeting is designed to extract high-level insights and granular to-dos.
The initial investment of 90-120 minutes at the outset of the project pays dividends down the road when we’re sailing through approvals and aligned on a launch plan.
Sprint Planning Meetings
We work in a 2-week sprint cadence. Each sprint starts with a planning meeting where we meet with your team to align on deliverables for that two-week period. Subsequent planning meetings will also include a demo of work completed in the previous sprint.
This cadence provides the team focused time to deliver meaningful work. It ensures we can proactively plan, pressure test design decisions and bug test new features more effectively.
In order to make the most of each sprint, we ask that you come to each planning meeting prepared to discuss what’s on deck, details about new priorities, feature requirements/specs and key dates.
Asana will provide the most up-to-date picture of our progress in a given sprint. If you ever have questions about a given task's status, you can check there.
This is also the best place to add new information or ask questions related to a certain task – it ensures the most relevant people are notified and in-the-loop. At the end of each month, Lena will issue a status report in Asana, detailing what has been completed over the last two sprints, and what’s on deck for the coming month(s).
Throughout the sprint, we may issue staging links for your review. These, and all other task-specific updates are shared via Asana.
Of course, this looks a little different at launch time, where we'll be more readily available.
In addition to Asana, agendas will also be circulated prior to our sprint planning meetings as well as a post-meeting recap following each get-together to ensure we’ve understood everything correctly.
From time to time, we also use Slack to connect directly with clients – but we ask that all feature requests and questions be communicated in Asana so nothing slips through the cracks.
Feature Requests, Urgent Updates and Bugs
Asana is our primary project management tool. It's a great, agile way to communicate, plan out milestones, and break down assignments.
While we'll all be working to keep everything on schedule, we know that in the world of ecommerce, things come up.
When they do, please log new requests using the Bug/New Task template in your Asana board.
Requirements & Prioritization
Once you have created a new task, you will be prompted to answer some short questions under the "Description" of the task – these questions will help us better address your request and properly assess prioritization.
We will then provide an assessment of when we will work on the new request.
If a request is urgent, we will re-prioritize other work in the sprint to make space for it. This will be a team effort and our success will depend on your collaboration.