Click to read notes
meeting with karim
introduce himself give a little bit of context around this approach that he’s taking. a product manager, have experience in different industries in regulatory / financial industry / different saas companies. steps we’ve done so far, the sense we have on this approach and give a high level overview about where we stand where we want to move from a project and a product perspective and what the expected outcomes are.
my contribution is to help gather the objectives and needs that are from the part of creating a sense of a product. the final end of this work is to offer a platform where artists can get a solution where they can meet the needs of reaching their audicence inside this ethical model.
we have identified certain problems that the artists have. we want to address those problems through the platform that we have. If we find a motive or a reason to address the roadmap of our platform, this will help us really identify the vision of our project.
here’s the doc
different users - subscriber, artist, label user, admin. what are the modules or group of modules needed for addressing these tasks. Created user personas.
broke down the activities and tasks in an information architecture kind of view. the information architecture is a living document that we have to keep updated. this will help us define an MVP. then we’ll be able to define the timeline based on all of this. We can then look at the different components to build out.
We can then build out a backend first that will enable merging justifay and resonate based on the needs of both organizations.
Si: How are we defining as an MVP. “Compete with Spotify” is not an MVP.
Karim: Once we have something that in a minimum way can do something. Focus on giving the current userbase a platform that keeps on working. To have that baseline, we will need to understand what is the current state of the current system. Possibly the current system already has components implemented we want to keep. Just to manage expectations, this is not going to be a big bang. We’re going to do this in an iterative way.
Si: good to know that the current state is going to be taken into consideration
Karim: what we are searching for is a way to give order and insight into all these feature rerquests and handle them in an appropriate way. We know that users requests and features on the business side have specific interests. Even the team proposes improvements and changes. Trying to handle that in an orderly way and give it a sense of product. That kind of approach will give us a chance to improve the product. It’s alligned with the philophy of the organizations.
David: from the Justifay point of view our interest is to deliver an MVP as fast as possible. We want to drag out that much the development. We want to have something the sooner the better. So of course that doesn’t mean we don’t care about the design. We want to focus on the core component to get started. We don’t want to invest two or three years if we can do something in a year.
rich: that timeline theoretically is revealed in the process of the work that Karim is working on. We don’t know what that timeline is now that timeline can become apparent.
Si: pointing out that dev estimates are hard but also that since we’re in an open source community, self dogfooding is a real thing for contributors.
David: we are looking for money. We’d hope to pay the people who are already working on it full time or part time. If we then still have money left we will hire other developers. All of these people should be working on the same approach. I think that’s how we grow stronger.
piper: boundaries between what’s going to be mvp and what’s not. iterative approach. referencing Jeremy’s doc
rich: specific question for Karim, research you’ve done so far with Jeremy’s documents and any study you’ve done of old documents and the current Resonate offer.
Karim: have done very high level research based on what I’ve been through based on what’s available in the community. I still haven’t developed a strong opinion on the current state of the stack. I haven’t reached that point yet. Once we have a better idea MVP wise we can identify the gaps and build on top of that. want to identify something that isn’t over-engineered.
side chatter about over-engineering.
brandon: I’m wondering just with this information being shared and then going back to our community with the notes and everything, how do we see this process moving forward, and how are we gauging the questions to help us inform how we formulate this MVP.
Karim: next is really to define a roadmap. It’s not realistic that we’re going to do everything. Idea is to have progressive delivery with one minimum baseline to build on top of that. In some cases to leverage on stuff that already exists. The final result of all this exercise is to also have a roadmap for the subsequent stages that we want the platform to evolve. That roadmap will need to continue living that needs to keep updating. The community evolves and the industry involves, and that needs to be adapted to those needs as well. The usual practice is to review roadmaps quarterly on the needs that stakeholders raise.
rich: I would like to reflect also on the history of the relation of justifay and resonate. as you define your mvp can you define to the aspects that are different between justifay and resonate?
Karim: definitely that’s a very good point. The platform gives service to both organizations. We know that there are going to be items and elements and components that will be common to both organizations. Some aspects can be shared. There are other specific components that will require organizational separation. Depending on the business model of each organization the general paradigm will be the same. We’re going to work together independently.
Anything we need to expand on? How do you feel about this overview.
rich: like to see some interaction in the future between the team that is building and talking about building in the Resonate context. Figure out how to have more conversations like this.
Karim: my expectation is that the more near we are for the definition for an MVP the more we’ll need input from community members. As a product manager it’s impossible to build a product by a product manager only. We need to do research, get input from users, the other stakeholders, the team that’s involved in building. All that information is very valuable and is part of the product.
rich: we’ve switched from a client relationship to a collaboration process. I know we’ve got people with really high expertise in the resonate community who I really hope do find a way to get involved in this process.
Karim: yes absolutely, this is part of a community that is bigger than us.
brandon: we want to get this in front of more people. Bring people into the conversation.