Hello all,
Over the past few months the Design team members at the Wikimedia Foundation (user experience [UX] designers, design researchers, user experience engineers, and communications) have been working with Arthur Richards from the Team Practices Group to identify the high-level themes that motivate design at the WMF. These themes have been turned into a brief statement of purpose, whose intent is to articulate the vision and purpose behind design at the WMF. This statement will influence the future direction of design work.
At this point the stakeholders are ready for a review of the draft statement. The purpose of this review is to gather a common understanding of its purpose, and to identify any key themes that may be missing from the high-level discussion. On the wiki page for the statement, you'll find these themes and what they encompass in the "Background" section. If you have an observation, comment, or concern about what is listed there, please bring it up on the talk page. If it is relevant to the review and understanding of the statement, it will be looked at for future drafts. If there are comments about design and the design process in general, we'll hold on to those until a time when they can be addressed for the broader discussion of design in general.
All that said, here are the links: * https://www.mediawiki.org/wiki/Design/Statement_of_purpose * https://www.mediawiki.org/wiki/Talk:Design/Statement_of_purpose
We look forward to seeing you on the wiki.
I'm going to ask this here since the talkpage on-wiki is a flow board and I find those very difficult to use, but I'm a bit unclear what the purpose of this is. All the things listed sound good in theory, but the language is ambiguous and very high level, to the point where it's hard to see how it applies in practice. Essentially, who is this for? What are the problems they are trying to address? What are they planning to do, and what will this mean in practice moving forward?
Thanks.
-I
On 10/11/16 18:40, Keegan Peterzell wrote:
Hello all,
Over the past few months the Design team members at the Wikimedia Foundation (user experience [UX] designers, design researchers, user experience engineers, and communications) have been working with Arthur Richards from the Team Practices Group to identify the high-level themes that motivate design at the WMF. These themes have been turned into a brief statement of purpose, whose intent is to articulate the vision and purpose behind design at the WMF. This statement will influence the future direction of design work.
At this point the stakeholders are ready for a review of the draft statement. The purpose of this review is to gather a common understanding of its purpose, and to identify any key themes that may be missing from the high-level discussion. On the wiki page for the statement, you'll find these themes and what they encompass in the "Background" section. If you have an observation, comment, or concern about what is listed there, please bring it up on the talk page. If it is relevant to the review and understanding of the statement, it will be looked at for future drafts. If there are comments about design and the design process in general, we'll hold on to those until a time when they can be addressed for the broader discussion of design in general.
All that said, here are the links:
- https://www.mediawiki.org/wiki/Design/Statement_of_purpose
- https://www.mediawiki.org/wiki/Talk:Design/Statement_of_purpose
We look forward to seeing you on the wiki.
Hi Isarra, thanks for the excellent questions. Here's my attempt to answer them:
The purpose of the statement of purpose is to gain clarity and build trust within the design group and with their principle stakeholders. With the statement itself, we seek to gain clarity and shared understanding about what design at the WMF is here for and trying to achieve (at a big-picture level). Through the process of defining the statement of purpose, we hope to build trust amongst the design group and with their principle stakeholders. So, the primary audience for this document is the design group itself, with the stakeholders of design being a secondary audience.
Moving forward, that is once the statement of purpose is done, design can take a close look at where it is now relative to where it wants to be as defined by the statement of purpose. Design can then use that difference to help make decisions about how we get from here to there (for instance to help in making decisions about staffing, structure, involvement in product teams, how to approach design problems, and so on).
Long story short, the statement of purpose is intended to be an organizing tool - to create clarity through everyone understanding the purpose, and trust by going through a collaborative process of definition amongst design and their stakeholders - so that they can execute better and with decreased friction.
A little more background and history: As the Foundation has evolved over the years, there have been many challenges and pain points around figuring out how design should function and how it should be integrated into the various facets of the organization (from product development to communications). Through all of the attempts to address those challenges and pain points over the years, it's become clear that the role and purpose of design is not well understood - at least not in a shared and consistent way, which makes it nearly impossible to find the right and lasting solutions. A few months ago, the Team Practices Group was asked to help identify and resolve the major pain points - after doing research, we agreed in conjunction with the design group that we should pursue clarifying the purpose of design and validate it with their stakeholders.
Does this answer your questions?
On Thu, Nov 10, 2016 at 12:24 PM Isarra Yos zhorishna@gmail.com wrote:
I'm going to ask this here since the talkpage on-wiki is a flow board and I find those very difficult to use, but I'm a bit unclear what the purpose of this is. All the things listed sound good in theory, but the language is ambiguous and very high level, to the point where it's hard to see how it applies in practice. Essentially, who is this for? What are the problems they are trying to address? What are they planning to do, and what will this mean in practice moving forward?
Thanks.
-I
On 10/11/16 18:40, Keegan Peterzell wrote:
Hello all,
Over the past few months the Design team members at the Wikimedia Foundation (user experience [UX] designers, design researchers, user experience engineers, and communications) have been working with Arthur Richards from the Team Practices Group to identify the high-level themes that motivate design at the WMF. These themes have been turned into a
brief
statement of purpose, whose intent is to articulate the vision and
purpose
behind design at the WMF. This statement will influence the future direction of design work.
At this point the stakeholders are ready for a review of the draft statement. The purpose of this review is to gather a common understanding of its purpose, and to identify any key themes that may be missing from
the
high-level discussion. On the wiki page for the statement, you'll find these themes and what they encompass in the "Background" section. If you have an observation, comment, or concern about what is listed there,
please
bring it up on the talk page. If it is relevant to the review and understanding of the statement, it will be looked at for future drafts.
If
there are comments about design and the design process in general, we'll hold on to those until a time when they can be addressed for the broader discussion of design in general.
All that said, here are the links:
- https://www.mediawiki.org/wiki/Design/Statement_of_purpose
- https://www.mediawiki.org/wiki/Talk:Design/Statement_of_purpose
We look forward to seeing you on the wiki.
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines New messages to: Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe
Okay, so you want to clarify... something, and build trust. What needs clarifying? What has been unclear? For whom, and building trust with whom? Are these even the right questions?
A problem here, from what you're saying, seems to be that things with Design have been historically overly complicated/confused, and there hasn't been good communication with other teams, with the community, even within Design itself. Though a step in the right direction, this seems to me like a continuation of that pattern, frankly. The more big words you use, the more passive voice, the more overarching 'themes' and less direct problem statements, the more you distance yourselves from what you're doing and who you're working with, and I would if anything strongly recommend the opposite. Keep it simple.
Your general purpose should be to make things... better. But what that means depends on what your problems are, so your problems are what you need to do work to sort out. That way you can address the problems, and move forward.
So what are the problems? How will you address them? And in order to define these problems, for that matter, what's your scope?
-I
On 10/11/16 20:36, Arthur Richards wrote:
Hi Isarra, thanks for the excellent questions. Here's my attempt to answer them:
The purpose of the statement of purpose is to gain clarity and build trust within the design group and with their principle stakeholders. With the statement itself, we seek to gain clarity and shared understanding about what design at the WMF is here for and trying to achieve (at a big-picture level). Through the process of defining the statement of purpose, we hope to build trust amongst the design group and with their principle stakeholders. So, the primary audience for this document is the design group itself, with the stakeholders of design being a secondary audience.
Moving forward, that is once the statement of purpose is done, design can take a close look at where it is now relative to where it wants to be as defined by the statement of purpose. Design can then use that difference to help make decisions about how we get from here to there (for instance to help in making decisions about staffing, structure, involvement in product teams, how to approach design problems, and so on).
Long story short, the statement of purpose is intended to be an organizing tool - to create clarity through everyone understanding the purpose, and trust by going through a collaborative process of definition amongst design and their stakeholders - so that they can execute better and with decreased friction.
A little more background and history: As the Foundation has evolved over the years, there have been many challenges and pain points around figuring out how design should function and how it should be integrated into the various facets of the organization (from product development to communications). Through all of the attempts to address those challenges and pain points over the years, it's become clear that the role and purpose of design is not well understood - at least not in a shared and consistent way, which makes it nearly impossible to find the right and lasting solutions. A few months ago, the Team Practices Group was asked to help identify and resolve the major pain points - after doing research, we agreed in conjunction with the design group that we should pursue clarifying the purpose of design and validate it with their stakeholders.
Does this answer your questions?
On Thu, Nov 10, 2016 at 12:24 PM Isarra Yos zhorishna@gmail.com wrote:
I'm going to ask this here since the talkpage on-wiki is a flow board and I find those very difficult to use, but I'm a bit unclear what the purpose of this is. All the things listed sound good in theory, but the language is ambiguous and very high level, to the point where it's hard to see how it applies in practice. Essentially, who is this for? What are the problems they are trying to address? What are they planning to do, and what will this mean in practice moving forward?
Thanks.
-I
On 10/11/16 18:40, Keegan Peterzell wrote:
Hello all,
Over the past few months the Design team members at the Wikimedia Foundation (user experience [UX] designers, design researchers, user experience engineers, and communications) have been working with Arthur Richards from the Team Practices Group to identify the high-level themes that motivate design at the WMF. These themes have been turned into a
brief
statement of purpose, whose intent is to articulate the vision and
purpose
behind design at the WMF. This statement will influence the future direction of design work.
At this point the stakeholders are ready for a review of the draft statement. The purpose of this review is to gather a common understanding of its purpose, and to identify any key themes that may be missing from
the
high-level discussion. On the wiki page for the statement, you'll find these themes and what they encompass in the "Background" section. If you have an observation, comment, or concern about what is listed there,
please
bring it up on the talk page. If it is relevant to the review and understanding of the statement, it will be looked at for future drafts.
If
there are comments about design and the design process in general, we'll hold on to those until a time when they can be addressed for the broader discussion of design in general.
All that said, here are the links:
- https://www.mediawiki.org/wiki/Design/Statement_of_purpose
- https://www.mediawiki.org/wiki/Talk:Design/Statement_of_purpose
We look forward to seeing you on the wiki.
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines New messages to: Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines New messages to: Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe
Well said. P
-----Original Message----- From: Wikimedia-l [mailto:wikimedia-l-bounces@lists.wikimedia.org] On Behalf Of Isarra Yos Sent: Thursday, 17 November 2016 2:16 AM To: Wikimedia Mailing List Subject: Re: [Wikimedia-l] Invitation to review: Design Statement of Purpose
Okay, so you want to clarify... something, and build trust. What needs clarifying? What has been unclear? For whom, and building trust with whom? Are these even the right questions?
A problem here, from what you're saying, seems to be that things with Design have been historically overly complicated/confused, and there hasn't been good communication with other teams, with the community, even within Design itself. Though a step in the right direction, this seems to me like a continuation of that pattern, frankly. The more big words you use, the more passive voice, the more overarching 'themes' and less direct problem statements, the more you distance yourselves from what you're doing and who you're working with, and I would if anything strongly recommend the opposite. Keep it simple.
Your general purpose should be to make things... better. But what that means depends on what your problems are, so your problems are what you need to do work to sort out. That way you can address the problems, and move forward.
So what are the problems? How will you address them? And in order to define these problems, for that matter, what's your scope?
-I
On 10/11/16 20:36, Arthur Richards wrote:
Hi Isarra, thanks for the excellent questions. Here's my attempt to answer them:
The purpose of the statement of purpose is to gain clarity and build trust within the design group and with their principle stakeholders. With the statement itself, we seek to gain clarity and shared understanding about what design at the WMF is here for and trying to achieve (at a big-picture level). Through the process of defining the statement of purpose, we hope to build trust amongst the design group and with their principle stakeholders. So, the primary audience for this document is the design group itself, with the stakeholders of design being a secondary audience.
Moving forward, that is once the statement of purpose is done, design can take a close look at where it is now relative to where it wants to be as defined by the statement of purpose. Design can then use that difference to help make decisions about how we get from here to there (for instance to help in making decisions about staffing, structure, involvement in product teams, how to approach design problems, and so on).
Long story short, the statement of purpose is intended to be an organizing tool - to create clarity through everyone understanding the purpose, and trust by going through a collaborative process of definition amongst design and their stakeholders - so that they can execute better and with decreased friction.
A little more background and history: As the Foundation has evolved over the years, there have been many challenges and pain points around figuring out how design should function and how it should be integrated into the various facets of the organization (from product development to communications). Through all of the attempts to address those challenges and pain points over the years, it's become clear that the role and purpose of design is not well understood - at least not in a shared and consistent way, which makes it nearly impossible to find the right and lasting solutions. A few months ago, the Team Practices Group was asked to help identify and resolve the major pain points - after doing research, we agreed in conjunction with the design group that we should pursue clarifying the purpose of design and validate it with their stakeholders.
Does this answer your questions?
On Thu, Nov 10, 2016 at 12:24 PM Isarra Yos zhorishna@gmail.com wrote:
I'm going to ask this here since the talkpage on-wiki is a flow board and I find those very difficult to use, but I'm a bit unclear what the purpose of this is. All the things listed sound good in theory, but the language is ambiguous and very high level, to the point where it's hard to see how it applies in practice. Essentially, who is this for? What are the problems they are trying to address? What are they planning to do, and what will this mean in practice moving forward?
Thanks.
-I
On 10/11/16 18:40, Keegan Peterzell wrote:
Hello all,
Over the past few months the Design team members at the Wikimedia Foundation (user experience [UX] designers, design researchers, user experience engineers, and communications) have been working with Arthur Richards from the Team Practices Group to identify the high-level themes that motivate design at the WMF. These themes have been turned into a
brief
statement of purpose, whose intent is to articulate the vision and
purpose
behind design at the WMF. This statement will influence the future direction of design work.
At this point the stakeholders are ready for a review of the draft statement. The purpose of this review is to gather a common understanding of its purpose, and to identify any key themes that may be missing from
the
high-level discussion. On the wiki page for the statement, you'll find these themes and what they encompass in the "Background" section. If you have an observation, comment, or concern about what is listed there,
please
bring it up on the talk page. If it is relevant to the review and understanding of the statement, it will be looked at for future drafts.
If
there are comments about design and the design process in general, we'll hold on to those until a time when they can be addressed for the broader discussion of design in general.
All that said, here are the links:
- https://www.mediawiki.org/wiki/Design/Statement_of_purpose
- https://www.mediawiki.org/wiki/Talk:Design/Statement_of_purpose
We look forward to seeing you on the wiki.
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines New messages to: Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines New messages to: Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe
_______________________________________________ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines New messages to: Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe
----- No virus found in this message. Checked by AVG - www.avg.com Version: 2016.0.7859 / Virus Database: 4664/13425 - Release Date: 11/17/16
I have only been peripherally involved with the process leading to this draft statement. My perception is that this statement is merely the first step, to lay a foundation for shared understanding. Once that has happened, then more interesting details will come. If this baby step is non-controversial, great. Any concrete actions and details will follow as separate documents (or other channels).
As for why this is necessary, consider the wording from the statement that they aim to make sharing knowledge "easy and joyful for everyone". That probably hasn't been expressed before, or discussed. While some might disagree that it's the right thing to do, it seems healthy to be transparent that it is the intent of design folks at the foundation.
Similarly, I appreciate knowing that the design folks advocate "rigorous research, and exploring innovative solutions". If nothing else, it might explain why a study is proposed, or why a new "crazy" off-the-wall idea is being floated out for feedback.
If you ignore all the prefacing and themes on that page, the actual statement is fewer than 75 words, in 4 sentences. It seems pretty simple to me, without a lot of jargon, passive voice, etc. It is high-level, intentionally.
Kevin Smith Agile Coach, Wikimedia Foundation
On Wed, Nov 16, 2016 at 4:16 PM, Isarra Yos zhorishna@gmail.com wrote:
Okay, so you want to clarify... something, and build trust. What needs clarifying? What has been unclear? For whom, and building trust with whom? Are these even the right questions?
A problem here, from what you're saying, seems to be that things with Design have been historically overly complicated/confused, and there hasn't been good communication with other teams, with the community, even within Design itself. Though a step in the right direction, this seems to me like a continuation of that pattern, frankly. The more big words you use, the more passive voice, the more overarching 'themes' and less direct problem statements, the more you distance yourselves from what you're doing and who you're working with, and I would if anything strongly recommend the opposite. Keep it simple.
Your general purpose should be to make things... better. But what that means depends on what your problems are, so your problems are what you need to do work to sort out. That way you can address the problems, and move forward.
So what are the problems? How will you address them? And in order to define these problems, for that matter, what's your scope?
-I
On 10/11/16 20:36, Arthur Richards wrote:
Hi Isarra, thanks for the excellent questions. Here's my attempt to answer them:
The purpose of the statement of purpose is to gain clarity and build trust within the design group and with their principle stakeholders. With the statement itself, we seek to gain clarity and shared understanding about what design at the WMF is here for and trying to achieve (at a big-picture level). Through the process of defining the statement of purpose, we hope to build trust amongst the design group and with their principle stakeholders. So, the primary audience for this document is the design group itself, with the stakeholders of design being a secondary audience.
Moving forward, that is once the statement of purpose is done, design can take a close look at where it is now relative to where it wants to be as defined by the statement of purpose. Design can then use that difference to help make decisions about how we get from here to there (for instance to help in making decisions about staffing, structure, involvement in product teams, how to approach design problems, and so on).
Long story short, the statement of purpose is intended to be an organizing tool - to create clarity through everyone understanding the purpose, and trust by going through a collaborative process of definition amongst design and their stakeholders - so that they can execute better and with decreased friction.
A little more background and history: As the Foundation has evolved over the years, there have been many challenges and pain points around figuring out how design should function and how it should be integrated into the various facets of the organization (from product development to communications). Through all of the attempts to address those challenges and pain points over the years, it's become clear that the role and purpose of design is not well understood - at least not in a shared and consistent way, which makes it nearly impossible to find the right and lasting solutions. A few months ago, the Team Practices Group was asked to help identify and resolve the major pain points - after doing research, we agreed in conjunction with the design group that we should pursue clarifying the purpose of design and validate it with their stakeholders.
Does this answer your questions?
On Thu, Nov 10, 2016 at 12:24 PM Isarra Yos zhorishna@gmail.com wrote:
I'm going to ask this here since the talkpage on-wiki is a flow board
and I find those very difficult to use, but I'm a bit unclear what the purpose of this is. All the things listed sound good in theory, but the language is ambiguous and very high level, to the point where it's hard to see how it applies in practice. Essentially, who is this for? What are the problems they are trying to address? What are they planning to do, and what will this mean in practice moving forward?
Thanks.
-I
On 10/11/16 18:40, Keegan Peterzell wrote:
Hello all,
Over the past few months the Design team members at the Wikimedia Foundation (user experience [UX] designers, design researchers, user experience engineers, and communications) have been working with Arthur Richards from the Team Practices Group to identify the high-level themes that motivate design at the WMF. These themes have been turned into a
brief
statement of purpose, whose intent is to articulate the vision and
purpose
behind design at the WMF. This statement will influence the future direction of design work.
At this point the stakeholders are ready for a review of the draft statement. The purpose of this review is to gather a common understanding of its purpose, and to identify any key themes that may be missing from
the
high-level discussion. On the wiki page for the statement, you'll find these themes and what they encompass in the "Background" section. If you have an observation, comment, or concern about what is listed there,
please
bring it up on the talk page. If it is relevant to the review and understanding of the statement, it will be looked at for future drafts.
If
there are comments about design and the design process in general, we'll hold on to those until a time when they can be addressed for the broader discussion of design in general.
All that said, here are the links:
- https://www.mediawiki.org/wiki/Design/Statement_of_purpose
- https://www.mediawiki.org/wiki/Talk:Design/Statement_of_purpose
We look forward to seeing you on the wiki.
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines New messages to: Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wik i/Mailing_lists/Guidelines New messages to: Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wik i/Mailing_lists/Guidelines New messages to: Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe
Hi Isarra, somehow I missed your email from the 16th and only just noticed it when I saw Kevin's response, which I think is totally spot on. I've added some additional responses inline below:
On Wed, Nov 16, 2016 at 4:16 PM Isarra Yos zhorishna@gmail.com wrote:
Okay, so you want to clarify... something, and build trust. What needs clarifying? What has been unclear? For whom, and building trust with whom? Are these even the right questions?
I mentioned this in my previous response: "With the statement itself, we seek to gain clarity and shared understanding about what design at the WMF is here for and trying to achieve (at a big-picture level). Through the process of defining the statement of purpose, we hope to build trust amongst the design group and with their principle stakeholders."
So - what's been unclear? What it is exactly that design at the WMF is trying to achieve at a big-picture level. Who are we trying to build trust with? Amongst people in the design group as well as their stakeholders (like product managers and software developers at the WMF, users and folks in the Wikimedia community).
A problem here, from what you're saying, seems to be that things with Design have been historically overly complicated/confused, and there hasn't been good communication with other teams, with the community, even within Design itself. Though a step in the right direction, this seems to me like a continuation of that pattern, frankly. The more big words you use, the more passive voice, the more overarching 'themes' and less direct problem statements, the more you distance yourselves from what you're doing and who you're working with, and I would if anything strongly recommend the opposite. Keep it simple.
Thanks for this feedback, it's helpful for me to hear. Do you think that the draft statement of purpose itself is overly complicated, or is it that the way we have been talking about this stuff (like on this thread) is overly complicated?
Overall I like the statement on wiki. Quick question though: "rigorous research" can be very time consuming, very expensive, and probably difficult to do well given Wikimedia's vast number of languages, number of projects, and multiple platforms. Could this be made more nuanced?
Other than that, I like what I see here.
Regards,
Pine
On Thu, Nov 10, 2016 at 10:40 AM, Keegan Peterzell <kpeterzell@wikimedia.org
wrote:
Hello all,
Over the past few months the Design team members at the Wikimedia Foundation (user experience [UX] designers, design researchers, user experience engineers, and communications) have been working with Arthur Richards from the Team Practices Group to identify the high-level themes that motivate design at the WMF. These themes have been turned into a brief statement of purpose, whose intent is to articulate the vision and purpose behind design at the WMF. This statement will influence the future direction of design work.
At this point the stakeholders are ready for a review of the draft statement. The purpose of this review is to gather a common understanding of its purpose, and to identify any key themes that may be missing from the high-level discussion. On the wiki page for the statement, you'll find these themes and what they encompass in the "Background" section. If you have an observation, comment, or concern about what is listed there, please bring it up on the talk page. If it is relevant to the review and understanding of the statement, it will be looked at for future drafts. If there are comments about design and the design process in general, we'll hold on to those until a time when they can be addressed for the broader discussion of design in general.
All that said, here are the links:
- https://www.mediawiki.org/wiki/Design/Statement_of_purpose
- https://www.mediawiki.org/wiki/Talk:Design/Statement_of_purpose
We look forward to seeing you on the wiki.
Keegan Peterzell Technical Collaboration Specialist Wikimedia Foundation _______________________________________________ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/ wiki/Mailing_lists/Guidelines New messages to: Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe
Hi everyone, a friendly reminder that if you would like to share your perspective on the draft statement of purpose https://www.mediawiki.org/wiki/Design/Statement_of_purpose, please do so no later than this coming Sunday, 27 November, 2016.
Big thanks to everyone who has been a part of the discussion so far :)
On Thu, Nov 10, 2016 at 10:40 AM Keegan Peterzell kpeterzell@wikimedia.org wrote:
Hello all,
Over the past few months the Design team members at the Wikimedia Foundation (user experience [UX] designers, design researchers, user experience engineers, and communications) have been working with Arthur Richards from the Team Practices Group to identify the high-level themes that motivate design at the WMF. These themes have been turned into a brief statement of purpose, whose intent is to articulate the vision and purpose behind design at the WMF. This statement will influence the future direction of design work.
At this point the stakeholders are ready for a review of the draft statement. The purpose of this review is to gather a common understanding of its purpose, and to identify any key themes that may be missing from the high-level discussion. On the wiki page for the statement, you'll find these themes and what they encompass in the "Background" section. If you have an observation, comment, or concern about what is listed there, please bring it up on the talk page. If it is relevant to the review and understanding of the statement, it will be looked at for future drafts. If there are comments about design and the design process in general, we'll hold on to those until a time when they can be addressed for the broader discussion of design in general.
All that said, here are the links:
- https://www.mediawiki.org/wiki/Design/Statement_of_purpose
- https://www.mediawiki.org/wiki/Talk:Design/Statement_of_purpose
We look forward to seeing you on the wiki.
Keegan Peterzell Technical Collaboration Specialist Wikimedia Foundation _______________________________________________ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines New messages to: Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe
wikimedia-l@lists.wikimedia.org