product framework

[Jean Kao]

Hi team,

Here's a basic framework I've been mulling over to help the teams focus on delivery and building product. I was thinking we could work individually with each team to help them break down their bigger ideas into digestible pieces and find concrete actionable items to move forward. Each of us (Peter, Judy, Jean) can tackle this with a project team.

1) Who's your main use case/user?

2) What does your product do? aka features

3) How does this benefit the user? aka benefits

All project teams should be clear on 1), 2), 3). To help clarify project teams should think about -

3) Scoping -

What can be accomplished in a year of hack nights? Anything longer is probably not going to happen.

4) Concept testing/user validation

This doesn't have to apply to all project teams. I think that project teams that are motivated by social impact (vs coding for fun, learning, etc) should do this. All project teams that want to be officially sponsored should have to do this. The core team will have to provide the connections and support to do this in a timely manner.

5) Technical feasibility/prototyping

All project teams should be do test this before going crazy on the coding.

6) Action plan (high level) for development

Again, I think is only necessary for the more "serious" teams or ones that want to be sponsored.

Thoughts on the framework or working with the teams?

Jean

[Jean Kao]

Okay team -

I basically put all these thoughts + Judy's comment on elevator pitch into a doc that we can test out with the larger projects.

https://docs.google.com/document/d/1GVZQNIm6xxrDN8i0EbecIOfiAg0FJbrifwt6EJrbfEg/edit?usp=sharing

Judy is going to approach the sugar mapping team about this on Wed 1/28 and I'm going to use this to help out the Open Referral/Social Services team that's been spinning their wheels for the past few weeks.

The goal here is to help focus the teams on exactly what they're doing and what they should be building.