A Day in the Life of a Web Marketing Lead at Blend
A Web Marketing Lead's day at Blend involves managing a variety of projects, using a "running list of tasks" and collaborating extensively via Slack with designers and developers. This iterative process, from initial design reviews ("Do we like the way this looks?") to post-launch analytics and improvement, allows for continuous learning and refinement of strategies across projects.
Project Management, Communication, Data Analysis, Teamwork, Problem-Solving
Advizer Information
Name
Job Title
Company
Undergrad
Grad Programs
Majors
Industries
Job Functions
Traits
Marisa Brazelton
Web Marketing Lead
Blend
California Polytechnic State University, San Luis Obispo
NYU Stern School of Business - MBA, Specializations in Tech Product Management, Leadership and Change Management, and Strategy
Business Management & Admin
Finance (Banking, Fintech, Investing), Technology
Communication and Marketing
Greek Life Member
Video Highlights
1. Web marketing leads utilize project management tools like to-do lists to manage their workload and maintain a sense of accomplishment.
2. Collaboration is key; professionals in this role heavily rely on communication tools (e.g., Slack) to interact with designers, developers, and other team members throughout a project's lifecycle.
3. A web marketing lead's responsibilities span the entire project lifecycle, from initial design and development to post-launch analysis and optimization, providing opportunities for continuous learning and improvement.
Transcript
What does a day in the life of a web marketing lead look like?
I think because I work on a variety of projects, I'm a big serial to-do lister. I have a running list of tasks and things that I need to accomplish. I generally try to keep it pretty short, so I always like to give myself a pat on the back, even if I've just accomplished one or two things that day.
I set myself up for good expectations because I am doing a lot of communicating at my company. We use Slack, so most of my communication with my coworkers takes place there. It's a lot of different conversations, whether it's one-on-one messages or group messages where we're trying to figure out based on the status of a project.
An example could be we have an event coming up and a landing page where people can register. Depending on the day, I could be working with the designers to figure out what the page looks like and reviewing that on a call with different people. We discuss if we like the way it looks or if we want to use different colors or images.
Or we might be working with our development team on the backend to actually build that page. We might be working with them to see if the designs match what it's looking like on the page. It could even be a post-launch process after the page is live and people are registering.
We're in the backend looking at the analytics of how people are interacting with it. We determine if we need to make improvements or if we're hitting our target number for registrations. It's definitely a continuous loop, which is fun to learn from. By the end of a project, you can take those learnings when you start a new one and see whether you design the page the same way or take a different approach.