I've had kind of a winding career path. I actually started college as a musical theater major before I moved into marketing. And so I think the first thing is that willingness to change and find the path that was most correct for me from a professional standpoint and taking something that was a passion and keeping that as a hobby. So I think that was the first thing that was kind of an incident and experience that shaped my career path. Next, I graduated in 2008 so that was right into the recession. And so I had big dreams of I'm gonna work at a big company and I'm gonna be a big VP. And instead, I ended up working in a startup that folded several months after I started working there just because the economy was not great. I think the willingness to adapt and explore all the options in my field, I ended up doing aviation. I ended up working for a presentation, design and training firm, and now I work at a tech company that makes collaboration software. So I think the biggest threat for me and getting to where I am today has been finding something to love in each job and love about each product or service and love about each customer that I'm going to serve.

I work across a variety of different platforms and disciplines within marketing. So I sit at the intersection. I do content strategy for social media, editorial press, live events, and speaking engagements. What that basically means is any time a message needs to go out to more than one place, I get called in to figure out how to do that. A lot of the deliverables are things like presentation decks, talk tracks and speeches for presentations long-form written articles and then short-form copy for a variety of social media channels. And I tend to speak at a higher level. So I think about industry trends. I think about things like teamwork, productivity and collaboration. I don't work specifically on products. That's a different team. For weekly work hours, I personally prefer to be in the office most of the time. I split my time between two offices here in the Bay Area, San Francisco, and Mountain View, usually in Mountain View, 3 to 4 days a week, and then up in the city one or two days a week. I usually get to the office somewhere between 8:30 and 9:00 AM and I usually leave the office around 5:30. I spend a lot of time in meetings. Actually, probably 50 to 60% of my time is in meetings, and then the other 40 to 50% of my time is spent working on deliverables at my desk. We have a really flexible work from home policy, in large part because we've got offices around the world and we're doing computer work. I do work from home occasionally. But that's not my personal preference, though. I have a couple of colleagues for 100% remote and then travel for work. I usually travel only a couple of times per year. My rule doesn't really require me to go out. It's not like fields or events where I need to be out traveling quite a bit. But I would say that I travel probably four times per year for somewhere between three and five days each time, for user conferences, for speaking engagements and then also to cover various events from a social, media and editorial perspective.

I'm working Atlassian, we obviously use our own tech stacks. So confluence is our internal wiki. That's where we do a lot of work. In the past, I've used tools like Google Docs or Office 365 that includes presentation software like Keynote and PowerPoint that includes Word or Google Docs. Those kinds of things. We also use Trello and Jira here. Those are both project management software tools. I really like both of those. Tello, in particular, is great from a marketing perspective because it allows us to link tickets. It allows us to link drafts. It allows to link illustrations directly within the board and then move them through the draft process of the reviews of the pitch process. In terms of the frameworks that we use, we use an SPI framework, the Situation Behavior Impact framework for delivering feedback. We also use a variety of frameworks. So one is called the DACI framework for decision making. Its driver, approver, contributor and informed. So most of those were kind of more well-rounded business frameworks that we use on a day to day basis or for project kickoffs. And then we also have what's called the team playbook here at Atlassian, that's a free resource that uses things to measure team health, gives us things like retrospectives to look back and see how a project performed and help us set goals and measures for things coming up over the next quarter.