V2MOM - Vision, Values, Methods, Obstacles, Measures

[afomi]

V2MOM

V2MOM, an acronym that stands for vision, values, methods, obstacles, and measures. This tool (pronounced "V2 mom") has helped me achieve my goals in my past work and helps make salesforce.com a success. Although there are many leadership paradigms and frameworks available to follow, V2MOM offers a new simplicity. It is easy to digest, unlike other programs that take longer to understand than they do to implement.

V2MOM enabled me to clarify what I was doing and communicate it to the entire company as well. The vision helped us define what we wanted to do. The values established what was most important about that vision; it set the principles and beliefs that guided it (in priority). The methods illustrated how we would get the job done by outlining the actions and the steps that everyone needed to take. The obstacles identified the challenges, problems, and issues we would have to overcome to achieve our vision. Finally, the measures specified the actual result we aimed to achieve; often this was defined as a numerical outcome. Combined, V2MOM gave us a detailed map of where we were going as well as a compass to direct us there.

Source

This issue will serve as our ongoing sounding-board for ideas related to the V2MOM proposition of the Website and Tools team.

Current Version: v1.0.0

EDIT: @therebelrobot - I'm gonna turn this thread into our full-blown V2MOM thread. Original Post contents are in the following comment.

[afomi]

Original Post

Opening this issue as a place to brainstorm ideas for the Presentation back to the core team in ~3 weeks.

Team Mission/Vision

• To enable the SF Brigade core teams with their goals using the technology portal of the site
• To ensure transparency of the organization through dissemination of goals and progress

Objectives by Dec 31, 2015 (~4 months)

• Enable sign up during events on the website #feature
• This supports engagement and data-gathering at events, which is used for reporting purposes #rationale
• Improve website accessibility #goal
• How can we measure this? #metric
• Run before and after checks with an A11y tool or something like http://www.508checker.com #feature #recurring-task
• More #todo

@therebelrobot, thank you for articulating goals per email!

I have one question about enable the SF Brigade core teams with their goals using the technology portal of the site. Is using the technology portal of the site a requirement?

I'd like to better understand:

• what tools are in place
• what user's current needs and frictions are around information
• what team habits and behaviors are in place (formal and informal)

[afomi]

Original Post

Opening this issue as a place to brainstorm ideas for the Presentation back to the core team in ~3 weeks.

Team Mission/Vision

• To enable the SF Brigade core teams with their goals using the technology portal of the site
• To ensure transparency of the organization through dissemination of goals and progress

Objectives by Dec 31, 2015 (~4 months)

• Enable sign up during events on the website #feature
• This supports engagement and data-gathering at events, which is used for reporting purposes #rationale
• Improve website accessibility #goal
• How can we measure this? #metric
• Run before and after checks with an A11y tool or something like http://www.508checker.com #feature #recurring-task
• More #todo

@therebelrobot, thank you for articulating goals per email!

I have one question about enable the SF Brigade core teams with their goals using the technology portal of the site. Is using the technology portal of the site a requirement?

I'd like to better understand:

• what tools are in place
• what user's current needs and frictions are around information
• what team habits and behaviors are in place (formal and informal)

[therebelrobot]

Is using the technology portal of the site a requirement?

I was just thinking since we're the website + tools team, that we'd be centered around that as the portal to what we build. Definitely up for discussion though.

• Site is currently a static site in Jekyll
• We will kind of need to see what the other teams come up with to see what their needs/frictions are
• ditto on habits/behaviors, though we can start by determining our own

I'm going to reach out to the rest of the core admin team and see if I can get a brief update to what their goals are and how we can help them. That will in large part build out our specific goals

On top of the goals currently listed, I wanted to see how you guys felt about assigning each of us to be a liaison for one of the other teams, stay keyed into their slack channel, attend their meetings, etc. and suggest tech solutions / provide assistance for tools / bring their concerns back to the w&t team. We're basically the support team for the support team, so I want to make sure they're covered with everything they need, as far as website/tooling is concerned.

[therebelrobot]

Is using the technology portal of the site a requirement?

I was just thinking since we're the website + tools team, that we'd be centered around that as the portal to what we build. Definitely up for discussion though.

• Site is currently a static site in Jekyll
• We will kind of need to see what the other teams come up with to see what their needs/frictions are
• ditto on habits/behaviors, though we can start by determining our own

I'm going to reach out to the rest of the core admin team and see if I can get a brief update to what their goals are and how we can help them. That will in large part build out our specific goals

On top of the goals currently listed, I wanted to see how you guys felt about assigning each of us to be a liaison for one of the other teams, stay keyed into their slack channel, attend their meetings, etc. and suggest tech solutions / provide assistance for tools / bring their concerns back to the w&t team. We're basically the support team for the support team, so I want to make sure they're covered with everything they need, as far as website/tooling is concerned.

[afomi]

I agree, @therebelrobot, that we'd likely focus on the site. Just wanted to be sure though.

And, ya, I'd like to liaise with the Project Launch team, lead by Larry, with Judy.

[afomi]

I agree, @therebelrobot, that we'd likely focus on the site. Just wanted to be sure though.

And, ya, I'd like to liaise with the Project Launch team, lead by Larry, with Judy.

[therebelrobot]

I can liaise with Member Support, for onboarding + etc.

(we may need to liaise with more than one until we can get more people on the team)

[therebelrobot]

I can liaise with Member Support, for onboarding + etc.

(we may need to liaise with more than one until we can get more people on the team)

[therebelrobot]

Ideas for further revision:

Vision

• To enable the SF Brigade core teams with their goals using the technology portal of the site
• To ensure transparency of the organization through dissemination of goals and progress

Value Prop / Value Add

• Add accessibility to site and tools
• Catalog existing resources and what is available
• be the gate-keepers for private resources donated to sfbrigade
• Liaison with other core teams to see what we can do to help them accomplish goals
• Assess the current state of usage on the site / tools (analytics, collect data)
• Based on that data, funnel traffic to most important areas

Methods

• Liaison with core teams, attend their meetings, record + make available meeting recordings
• find and use appropriate testing tools for accessibility
• implement google analytics, add hooks to EVERYTHING
• learn each of the donated resources, and how to allocate them securely

Obstacles

• time
• communication (internally and with other core teams)
• momentum
• scheduling - syncing our schedules with each other and with other teams

Measures / Metrics

• Any ideas, no matter how small, tracked in github
• Set up and regularly use accessibility testing tools
• 100% attendance in liaisoning core team meetings
• Weekly meeting for w+t team, outside of liaison meetings
• Collected a MASSIVE amount of analytics data for processing
• Lean down the site, make it more purpose-driven
• Never let any PR on website age 72 hours without some type of response / tagging

[therebelrobot]

Ideas for further revision:

Vision

• To enable the SF Brigade core teams with their goals using the technology portal of the site
• To ensure transparency of the organization through dissemination of goals and progress

Value Prop / Value Add

• Add accessibility to site and tools
• Catalog existing resources and what is available
• be the gate-keepers for private resources donated to sfbrigade
• Liaison with other core teams to see what we can do to help them accomplish goals
• Assess the current state of usage on the site / tools (analytics, collect data)
• Based on that data, funnel traffic to most important areas

Methods

• Liaison with core teams, attend their meetings, record + make available meeting recordings
• find and use appropriate testing tools for accessibility
• implement google analytics, add hooks to EVERYTHING
• learn each of the donated resources, and how to allocate them securely

Obstacles

• time
• communication (internally and with other core teams)
• momentum
• scheduling - syncing our schedules with each other and with other teams

Measures / Metrics

• Any ideas, no matter how small, tracked in github
• Set up and regularly use accessibility testing tools
• 100% attendance in liaisoning core team meetings
• Weekly meeting for w+t team, outside of liaison meetings
• Collected a MASSIVE amount of analytics data for processing
• Lean down the site, make it more purpose-driven
• Never let any PR on website age 72 hours without some type of response / tagging

[therebelrobot]

@sfbrigade/website-tools Any thoughts on these ideas so far?

Also, got a list of the other core teams and their leads. We'll want to each pick at team to liaison with, and reach out to their lead and see when they're meeting next so we can be involved with it. We'll also want to flesh out what we as w+t liaisons will be doing, and how we'll bring it back to our meetings.

Team	Lead	W+T Liaison
Executive	Jesse Biroscak or Maddy Suda	Jesse @jszwedko
Member Support	Julio Feliciano	Trent @therebelrobot
Project Development	Larry Bafundo	Ryan @afomi
Hack Night	Michael Guia	Shared

[therebelrobot]

@sfbrigade/website-tools Any thoughts on these ideas so far?

Also, got a list of the other core teams and their leads. We'll want to each pick at team to liaison with, and reach out to their lead and see when they're meeting next so we can be involved with it. We'll also want to flesh out what we as w+t liaisons will be doing, and how we'll bring it back to our meetings.

Team	Lead	W+T Liaison
Executive	Jesse Biroscak or Maddy Suda	Jesse @jszwedko
Member Support	Julio Feliciano	Trent @therebelrobot
Project Development	Larry Bafundo	Ryan @afomi
Hack Night	Michael Guia	Shared

[jszwedko]

Thanks for writing these out! Overall I feel like this is a good amount of work to shoot for for the next 11 weeks.

V2MOM thoughts

I'm 👍 as I was when we discussed them, but some specific thoughts:

100% attendance in liaisoning core team meetings

I was thinking about this a little bit more. I really like the idea of being liaising with the other teams, but I think attending every one of their meetings may not be a tenable idea for the following:

• It makes sense for them to schedule their meetings when is convenient for them which may not be for the liaison
• A lot of their meeting agenda likely will not involve us directly so sitting in on their meetings may not be an effective use of our time

My suggestion is:

• Be part of that team's slack channel (if they have one)
• Be in regular contact with each team's lead (what this means can depend on how the liaison+lead involved, it could be meeting in-person, voice calls, or e-mail)
• Receive their meeting notes if they keep them
• Could still sit in on their meetings if there is something especially pertinent

Assess the current state of usage on the site / tools (analytics, collect data)

I think this will help greatly in figuring out what to concentrate on with the site.

Liaising

I think it'll be easy to liaise with Michael since at least one of us will probably be present at each Hack Night so we could share that one. I can take responsibility for liaising with the executive team.

[jszwedko]

Thanks for writing these out! Overall I feel like this is a good amount of work to shoot for for the next 11 weeks.

V2MOM thoughts

I'm 👍 as I was when we discussed them, but some specific thoughts:

100% attendance in liaisoning core team meetings

I was thinking about this a little bit more. I really like the idea of being liaising with the other teams, but I think attending every one of their meetings may not be a tenable idea for the following:

• It makes sense for them to schedule their meetings when is convenient for them which may not be for the liaison
• A lot of their meeting agenda likely will not involve us directly so sitting in on their meetings may not be an effective use of our time

My suggestion is:

• Be part of that team's slack channel (if they have one)
• Be in regular contact with each team's lead (what this means can depend on how the liaison+lead involved, it could be meeting in-person, voice calls, or e-mail)
• Receive their meeting notes if they keep them
• Could still sit in on their meetings if there is something especially pertinent

Assess the current state of usage on the site / tools (analytics, collect data)

I think this will help greatly in figuring out what to concentrate on with the site.

Liaising

I think it'll be easy to liaise with Michael since at least one of us will probably be present at each Hack Night so we could share that one. I can take responsibility for liaising with the executive team.

[therebelrobot]

I think attending every one of their meetings may not be a tenable idea

Fair point. I'll leave that out of the first version of the slides.

Also, updated the table above with your liaise team.

[therebelrobot]

I think attending every one of their meetings may not be a tenable idea

Fair point. I'll leave that out of the first version of the slides.

Also, updated the table above with your liaise team.

[therebelrobot]

Kk. Locking down v1.0.0 of V2MOM for the presentation tonight. I'll add this into our repo for future usage, and will link here in a second.

EDIT: Current V2MOM Version: v1.0.0

[therebelrobot]

Kk. Locking down v1.0.0 of V2MOM for the presentation tonight. I'll add this into our repo for future usage, and will link here in a second.

EDIT: Current V2MOM Version: v1.0.0

[afomi]

looks great - the only feedback

Lean down the site, make it more purpose-driven, implement google analytics, add hooks to EVERYTHING

This sounds like 2 different methods that subtly at-odds as one.

• Lean down the site, make it more purpose-driven
• Improve analytics by implementing google analytics and adding hooks to EVERYTHING

Catch you tonight!

[afomi]

looks great - the only feedback

Lean down the site, make it more purpose-driven, implement google analytics, add hooks to EVERYTHING

This sounds like 2 different methods that subtly at-odds as one.

• Lean down the site, make it more purpose-driven
• Improve analytics by implementing google analytics and adding hooks to EVERYTHING

Catch you tonight!