What stakeholders does this project have?ĭistinguish roles at a high level with three separate lists: core team, stakeholders, and interested parties. Who will be contributing to this project? Who will have input on the development of this project? Your participants should include everyone involved in the development of your project. These are the goals of your team or company, which may or may not match the goals of your users. Begin by listing project goals, then move on to more specific program or product goals. The goal of this project may be a part of a larger goal. In what way will achieving these goals change what you offer to your users?įor many design and UX projects, the project itself is actually part of a larger body of work. Your project’s goals are different from the benefits listed previously, which are user-defined, and narrower in scope. Goals are high-level statements that provide the overall context for what the project is trying to accomplish. Add more context to these benefits by stressing the impact they will have on your users. Benefits may not affect all users in the same way - take time to outline what the benefit will be and use connector lines to link the benefits to their beneficiaries. Will these benefits be temporary? Or will your users continue to benefit after the project is released?įocus on benefits that are well-defined and relatively certain. How much of an impact on their experience with your product can your users expect from this project? What will your users gain from this project? Phrase these benefits as what the user will expect, not what you intend to deliver. List the concrete benefits that users will have when the project is successfully completed. Include more specific qualities of your users, like distinguishing characteristics or qualities. You can include user persona profiles you have developed, or users can be listed as target groups or segments of larger groups. What are some common characteristics, traits, or behaviors of these groups? How do these commonalities define these users? In what ways do users organize themselves as groups? Who will be interacting with your project? These can be defined at a high level, such as “readers” and “advertisers” for a media portal, or you may want to be more granular in detail - for instance, you can list personas you’ve developed. Use this section to identify the main target groups relevant to your project. (Learn more about customizing Stormboard templates here). Like all of Stormboard’s templates, the individual sections can be resized as needed (without affecting the content that has already been added), and you can add sections to any of the sides of the template if you have an area that you want to cover that is not already built into the template. Stormboard’s Project Canvas Template is divided into 10 sections: Users, Users Benefits, Goals, Participants, Activities, Deliverables, Risks, Milestones, Constraints, and Scope. Using Stormboard’s Project Canvas Template It should be used to stay on top of the project’s development, stay ahead of any potential conflicts or redundancies, and improve communication throughout the team. The Project Canvas is for anyone who is working on a project together and is meant to be used throughout the project - not only at the beginning. Project management is a challenge - there are countless moving parts, and it is easy to get off track if you don’t have the goals and parameters of your project clearly defined.ĭeveloped by Jim Kalbach, a UX strategist, in 2012 , the Project Canvas was created to give everyone working on a project a view of not only the goals and individual elements of the project, but the relationships between them at-a-glance, so that the entire team can stay aligned in their work.
0 Comments
Leave a Reply. |