Thinking About A Website Relaunch? Think Again!
Is your marketing team missing critical opportunities?
- Does your marketing team struggle to keep up with incoming demands?
- Are you investing a disproportionate amount of budget toward non-website opportunities?
- Are you limited to working on one task at a time?
- Does your website development workflow lack guardrails?
- Are you on-call 24-7 when things break?
- Does each major change require weeks of planning?
We remove relaunch friction by applying our agile processes of ideation and frequent releases using Pantheon’s workflow so you can focus on growing your business.
What does success look like?
Molly Duggan Associates WebOps team completes your projects with Agile tools and processes using one cross-functional team, iterating towards the same goals.
Get started by defining the greatest impact on your ability to grow your business
- Make it specific and measurable.
- Define your project owners and stakeholders.
- Who is your audience?
- What do you want your audience to do?
- How does your website fit into your business plan?
- Do you have the right team in place?
- What does done look like?
- Rinse and repeat
Featured Questions
We use Pantheon’s multidev cloud environments for each customer request. The environments are labeled according to the ticket number assigned so anyone on our team can quickly jump in and assist. Each feature release goes through internal development and QA cycle, then customer review and approval cycle, and finally, we deploy the new feature release to the LIVE environment.
Building a WebOps culture can be exciting and challenging. Essentially, everyone whose job it is to change a website in significant ways (code, visuals, content, success measurements) should think of themselves as one cross-functional team, iterating towards the same goals.
Everything starts with a project owner or director building a team that would consist of a product marketing manager, UX designer, web developer, marketing operations manager, and a demand generation manager. Smaller organizations may find that one person owns multiple rolls.
Appointing a single decision maker is key to making fast decisions. Making decisions by committee will take longer and defeats the purpose of WebOps.
Work with your new WebOps team to define your customer pain points. How does your organization respond to your customers’ pain points with solutions? If you have personas built out already, this is a great place to start. You’ll want to create or refine those existing definitions. Then, run these personas through a needs assessment. What are their pain points? How does your business respond to their needs or solve their problems? Be as detailed as possible here so that you can start to identify themes and prioritize areas of focus.
Never look at your persona work as being complete. You should regularly test assumptions you have about your audience and connect with them as much as possible to understand who they are and what they need from you.
Determine if you need to hire an agency that will provide additional expertise to ensure success and/or meet tight deadlines. You should be able to expose gaps where your team may lack experience or expertise. Does this project require additional support? Are you at risk of missing your target deadline due to lack of resources? Hiring a dedicated agency can seem like a big expense, but in reality their subject matter expertise may actually save you time and money in the long run because they will know what works and what doesn’t in ways your existing team can only uncover by trial and error.
