Are you “dogfooding”?

DogfoodingDogfooding” (or “eating your own dogfood”) refers to a company’s use of its own products in order to discover usability problems, poor customer experiences, inelegance, etc.

Are you dogfooding? If not, you should be.

I’d argue that a marketing department should do more than just use its company’s products; it should also follow the company’s customer-facing communication, participate in its programs, etc.

Here are some ways you can (and should) be dogfooding:

Continue Reading

NEW: Project Status & Priority Levels

Hi Marketing Team,

We have a massive amount of work flowing through our department at any given time and the priorities change rapidly. Phil and Nathan have asked the marketing leads to make sure they are aware of every project that we’re working on. On a weekly basis the leadership team will be looking at all projects that have come into our department and will set priorities for them to make sure we’re all working on the most important projects.

This means that the Wiki is becoming even more important because it is the only place where we can see every project that is going on.

1)      Every project needs to have a Wiki page. Nathan has asked Design and MarTech to push back if there isn’t a Wiki associated with a project*

2)      We’re making some changes to the way we use the project status field on the Wiki

  1. Triage: every new project needs the status set to triage. Management will determine whether we need to do it now or later. The templates should all be set to triage. Please do not change this.
  2. Pending: once a project has been triaged, if Phil and Nathan want it to be worked on now, we’ll changed the status to pending, assign it to someone to own and assign a priority level.
  3. Active: once you start working on a project that has been assigned to you, you’ll need to change the status to Active. All active projects should have a priority level assigned to them.
  4. d.      OnHold: we will no longer be using this status
  5. Backlog: Backlog projects are ones that we have decided not to work on at this time. We will be changing these Wiki pages so that they are not assigned to owners, but are instead assigned to areas of ownership. When a backlogged project is ready to be worked on  it will move to pending (if no work has been done yet) or to active (if some work was done on it before it was backlogged).

3)      We’re adding priority level to every Active project on the Wiki: [[projectPriority::]]

1: On Fire

2: Do now

3: Do later

*We still differentiate between a task and a project.

  • Tasks: A task is something that needs to get done that is isolated to a single individual or a single “thing”. If something requires more than one individual to be involved, or has multiple steps, then it is not a task it is a project. Tasks can exist outside of projects. These do NOT require a Wiki.
  • Projects: A project is a collection of tasks. These require a Wiki.
  • Bugs: Things that are broken on websites, landing pages, in software, etc. These do NOT require a Wiki.

For webpage updates: If it is changing the design or structure of a page it is a project. If it is content it is a task.

Product Team: This change does not apply to sku Projects and Sermon Archive Projects.

Who’s My Boss?

From: Phil Gons
To: Marketing Dept

As I stressed in our department meeting last month, it’s important that you understand who your boss/supervisor/manager is (yes, I’m using those interchangeably). Most of you probably have a team lead and a manager. While your team lead is likely more involved in overseeing your day-to-day work, your supervisor is your boss.

For now, your boss is either Nathan Elson, Nick Kelly, or I. Even if you’re confident you know who your boss is, please take a moment to find your name on http://wiki/Marketing_Supervisors. Then make sure your personal wiki page accurately reflects that.

Thanks!

Phil