-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discussion: Updating the Marketing team description #87
Comments
@eidolonnight could you please add a link and summary from the two meeting this has been discussed at. I added this card as a reference to today's agenda (card #86) to invite people to add suggestions. Thank you Nicholas.Contributors coming to this card, please add suggestions directly to this card. You only need a GitHub account to do this. Thank you in advance. |
I've been thinking about this a bit since it first came up. Looking through some of the feedback from the previous Slack discussions linked above, plus taking a tour around what other teams have done to get a baseline, I've drafted some words for consideration. A quick observation about the Marketing descriptionI noticed that the Marketing description on the "Get Involved" page is different from what's noted above in the Welcome Box/Handbook. This doesn't seem to be the case for most other teams. The trend appears to be:
I looked at a few different teams, but some of the ones that stood out as examples were Documentation, Accessibility, and Design (if others wanted to take a look). Copy suggestions for the "Get Involved" pageHere are a few variations I've been playing with:
Copy suggestions for the Welcome Box/HandbookI'd propose using whichever option above feels the most accurate, then adding a section to expand into more specifics (for the following example, I'm using Option 1 from above):
Looking forward to seeing what people think! 😃 |
Thanks for your work on this @thetinyl!
For the Handbook, adding that additional section is also really helpful. It's a great way of guiding people into all things marketing. Nice work 😄 |
As I said in Slack, I think that our existing descriptions could maybe be better. For example, we market WordPress to the wider world, but also to the people already within the WordPress ecosystem. We could probably be more specific about what we market too. For example, we don’t market specific themes or plugins for individuals/companies. Our focus is on features, programs, and efforts that are core to the project. Thank you @thetinyl for some initial explorations here.
I really like "supports the growth and maintenance" as it touches on the fact that we are both growing our audience as well as performing important maintenance work that supports the project. I also love that you spell out "current and future users, extenders, and contributors." so our audience is clearly defined.
I think there is some room for improvement in this line though. The "from this to this" is a bit too broad to be useful, but also specific enough to be limiting. It might make more sense to get at the heart of what marketing does. I see that as developing, executing, and monitoring programs and campaigns that promote the use and development of WordPress. We are not just a resource for strategy. We take action and are accountable for those actions (Ie. we monitor the results). We're not only showcasing content from other teams, we are creating content. The specifics of this can then be expanded in our welcome box with the other line from above, which may change with some regularity as our projects change. So I'm thinking something like the following:
|
Thanks for thinking about this and starting to draft some words, @thetinyl! Of the three options above, the second one (Option 2) seems to me to be the most accurate. However, I like @eidolonnight's suggestion to get to the heart of what marketing does and to include the specifics in the welcome box. I also wonder if, besides including the expanded description in the welcome box, we can provide a little more clarity on the relevant resources/links to new visitors and contributors. That is, where they can learn more about what the Marketing team does, the current projects, and how to collaborate. Maybe it's a bit long but, for example, I like how the Documentation team also provides an overview of the most important resources. Just a suggestion that I think can complement the effort to improve the description of the team. 🙂 |
I like this for its succinctness:
However, I am missing the presence of the community in this, which was present in some earlier iterations. One could argue that "the WordPress project" as a whole encompasses the community, but in my experience/IMO most people think of the project as the software and the community as the people. I liked the differentiation between platform and community for this reason. Additionally, specifying "the platform" emphasizes the narrower scope of the core platform, and not the wider ecosystem. So perhaps expanding on that, with a few tweaks back to previous language (changes bolded):
Note, this would also serve as a good litmus test for making marketing decisions in the future:
|
This is interesting. Thanks @sereedmedia . I was indeed considering the community as part of the WordPress project.
I do not think we should use pint 1 as a litmus test, but we have in the past. The problem is that this quickly becomes too broad. In the last few months we've seen requests to promote individual plugins, corporate events, publications, etc. Would helping a theme author, a member of the WordPress community, promote their theme, pass that litmus test? Many people seem to think so, and I understand their confusion. That is however not this team's purpose. Expanding on the example above, we may promote WordPress to theme authors and share things like calls for testing from the Themes team. We would not help promote an individual author's theme. On top of it not being a part of our purpose, it's far too difficult to do equitably. This is why I had trouble explicitly using "community" in any of my drafts. We do promote the community, but only within the confines of the project. Edit: BTW I like the proposed "creates" way more than "develops". |
@thetinyl Thanks for sharing drafts on this. I especially resonated with the handbook copy "The WordPress marketing Team markets WordPress and its community to the wider world. 1. I love alliteration in marketing copy; studies show it aids in recall! 2. To the point, clear, punchy. I think my favorite option shared was no. 3
But wonder how to bridge the gap between that and Sé's comment above. Perhaps something like The Marketing team supports the growth of the WordPress open source Project and its community. From helping other teams share their programs and initiatives, to highlighting the benefits of the platform and community for current and future users, extenders, and contributors. |
Personally, I'm torn between @eidolonnight's suggestion and @sereedmedia's variation that solves for the "community" often being missed despite being implied. I'd be happy to throw my vote behind either. For @eidolonnight's version, I do think my preference would be for Sé's word choice: "creates" over "develops", and "development" over "maintenance". I'd also consider the following change in bold, just to cut down on words a bit further:
For @sereedmedia's version, I'd also suggest the same word change as above, plus adding punctuation to break up the long sentence (changes in bold):
As an aside: I also agree with @rmartinezduque's idea about expanding the Welcome Box further to link off to relevant resources. Is that something we should open another Github issue about (once this one closes)? Or continue discussing here? |
If we add platform and community, which are specific to WordPress, we might want to edit the last part for brevity adjusting it to existing and future audiences rather than "current and future users, extenders, and contributors." But in reading the newer comments especially from @sereedmedia if there is a perception problem of the project being platform(software) and community(people) that means there is a miss somewhere in what the project is. I would venture a guess that if/when we use the word project we'd like for people to associate it with both things, and we have a first chance to amend that with some of the revised copy. |
Thank you to everyone who has chipped in her. I do want to take a moment to re-state the goal of this description edit because it is the lens that we should be reading these through:
Over the last year, I have heard accounts of, and personally experienced, new incoming Marketing team contributors being confused about what our team does. Sometimes that confusion is about the tasks we're working on, which is already being addressed with our work in Github and our new meeting format. Many times the confusion about our team's purpose and general focus (Ie. people think we are working on, or will support, initiatives that we do not). This confusion takes numerous forms. New contributors may think that we will help them promote their plugin, theme, event, or company because they are "part of the community". New contributors think that our primary goal is only to attract new WordPress users, or that we only market to developers, or that we only speak to site builders, etc. New contributors may assume that we have control over the website, SEO, or a variety of other systems typically related to marketing. My goal with a new description is to be specific and clear about what our team does, and of course implicitly communicate what we do not do.
@thetinyl I feel very strongly that "community" should not be a separate item because we only promote "community" within the confines of the project. The current team description has a proven record of causing confusion, and I think this is part of it (as mentioned here: #87 (comment)). Plus, we have a Community team that "supports the community".
@jpantani I like that this keeps getting shorter, but I do think we run the risk of people not understanding who our audiences are. Specifically mentioning "current and future users, extenders, and contributors" helps incoming contributors understand that we're not just marketing to new potential users, and it helps other teams understand that we are not just speaking to current project developers.
@thetinyl I'm not totally against swapping "programs and campaigns" with "initiatives", but it does seem like a missed opportunity for further clarity and the introduction of marketing terms. Could you elaborate on the word choice here? |
Thank you @eidolonnight for following up on this. I'd put my vote behind this text:
I also think we should put effort into transmitting what “extenders” are especially in relation to “contributors”. I know Josepha has spoken about it in the past and Mark wrote a post on the P2 about further explaining it, but I’m not sure it’s very clear to our general audience. |
@eidolonnight has shared today that it is the last week to add any feedback to this discussion. It will then go to Josepha for consideration. Please add your comments. |
@eidolonnight That's an interesting perspective. Primarily, it felt like a sentence full of lists, and that made it a bit cumbersome to read. Out of all the places to be a little less specific, that felt like it would impact the message the least. I do think it's okay to be a little all-encompassing, given the rest of the message feels focused and clear. However, if "initiatives" does feel too vague, I'd still suggest sticking to one word. If we're talking marketing terms, "campaigns" feels much more obviously marketing-y than "programs" (which exist elsewhere in the community). Also thinking about where this description will live (likely in 3 places: Make page, Welcome Box, Handbook), it will have additional content for context most of the time. |
@eidolonnight is there an update on this issue please or do you have a preferred date when we could come back to it? Thank you. |
In my experience, "community" does not at all imply plugins or themes, that is usually covered by the term "WordPress ecosystem". But if it's too controversial to say community, then I like the line that @murillol referenced above:
However, I think that extenders are users, and technically, so are developers. "End-users" are the actual "users" we are differentiating between here. I don't think extenders is understood enough in parlance to be useful. Also "contributors" could be interpreted to mean the community (see FFTF discussion) and folks who contribute to the ecosystem, so I think that covers developers as well. I also like "initiatives" because it allows for a variety of ways for the Marketing team to accomplish its goals. So and thus, I like this slightly streamlined version: The Marketing team creates, executes, and monitors initiatives that promote the growth and development of the WordPress project to current and future users and contributors. |
Agree..
I like this one too! |
What is the timeline for this discussion and eventual adoption? |
When this is updated. Can the update be added to this page of the Handbook too. Thank you. https://make.wordpress.org/marketing/handbook/about/ |
Looks good to me. "Initiatives" still doesn't feel like the right word to me, but I'm happy if everyone else is happy. With the introduction of our new team reps, I'm going to update the assignees for this issue. I believe the next steps are:
|
Final call for contribution to this discussion! All comments/ideas/concerns etc are welcome before 26 January 2023. After this point, team reps will review and consolidate the discussion and move forward with the new team description according to the steps outline by @eidolonnight above. |
Thank you to all the contributors on this thread. Creating a team description that represents our work is important, and there has been a lot of great dialog and contribution on this GH issue. After issuing the last call for contribution, Team Reps reviewed the complete thread and discussed all that contributions that were shared. With that said, we have finalized the proposal for an updated team
Our next steps are as follows:
Thank you again to everyone that contributed to this conversation. <3 |
Hello, apologies. I have opened this card and saw my contribution was still sat in the draft. My additional thoughts for reflection.
|
Thank you so much for sharing your draft and thoughts with us @nalininsbs. I definitely hear your perspective and value the time you took to share this. We did a last call for contribution so I will leave the issue closed for now to be fair to the group and help keep the forward momentum. |
Discussion on updating / revising the descriptor of the team that appears in the Marketing Team Handbook.
Current descriptor
The Marketing team focuses on making WordPress marketable in all sorts of contexts, from the WordPress.org side all the way to core and the wider community. We market WordPress and its community to the wider world.
6 July 2022: Discussion in Slack https://wordpress.slack.com/archives/C0GKJ7TFA/p1657121780284969
13 July 2022: Discussion in Slack
The text was updated successfully, but these errors were encountered: