Power/Interest Grid and Customer Grouping with Segmenting Canvas

Hello and welcome to yet another KBD blog post! In the workshop last Wednesday, we went through stakeholders and made some maps to visualize the importance of different stakeholders in our assignment. This week we have already had another meeting with our contact from Solita. In our meeting we talked about the upcoming interviews and we got some clarification on our assignment. We are no longer focusing only on software development projects and our new topic is “How to boost learning and knowledge sharing in between projects?”.

In this blog post, first we will be talking about the stakeholders on our assignment and then we will focus more on this week’s meeting with our contact and the change of our assignment topic. 

 

In this week’s workshop we did Power/Interest Grid on our stakeholders and Customer Grouping Segmentation canvas which are presented in the pictures below. 

 



 

In the picture above is our Power/Interest Grid, in which we have divided our stakeholders in a grid based on their power and interest in our project. With this division we are able to see more clearly which stakeholders are more important to keep informed and managed closely and which ones we should make sure are satisfied. With this prioritizing we are able to use our resources more efficiently (Mind Tools 2021).

 

We found Co-working partner organizations and technical and project support as low power and low interest stakeholders. We see that our focus should be more on the actual people who are developing and using the product such as end-users and customer organization. They have more interest in the project but still quite little power. That makes them stakeholders that should be informed during the project. Regulators on the other hand have more power over the project but they are not that interested. We should keep them satisfied by following the rules they have set but they don’t need to be informed as much as the others. Then there are Solita and the development team, which are high power and high interest stakeholders. They should me managed closely during the project. Luckily, we have an active contact from Solita and with his help it is possible to be in contact with Solita and the development department. 

 

In the picture below we have assembled a segmentation canvas on customer grouping. 

 



 

We found two main groups with customer grouping. The teams working on different projects at Solita are important because they work at the center of the problem, we are trying to find solutions to. Problems might occur if we can’t get enough and accurate information from this group related to the problem. The other group is Solita as an organization and especially the contact we have from Solita. This group is crucial as a connection to the teams working at Solita and the information we need from the company to be able to find working solutions.

 

Even though we did not have much time to do the customer grouping in the workshop we still managed to find these groups and analyze their effect on our project. After all the point of customer segmenting is to be able to see which customers to target and from which we could get useful information with our upcoming interviews (Koski 2015).

 

In our latest meet with our contact from Solita we focused our assignment to consider the knowledge sharing in between projects as before it was about knowledge sharing in a software development project. This allows us to not focus too much on the software project structure, but the change makes the assignment a bit more extensive. Our contact had some ideas on who could be useful people to interview on this subject from Solita and we started to search for available slots in our schedules. We decided to have about three interviews with just one interviewee and two focus group interviews. 

 

This week our team contributions have divided evenly. We have found it easiest to share responsibilities each week because we are all quite busy with other courses and finding time to make everything together is hard. We have had one meeting with our contact this week and a short meeting with our team right after the meet with the contact. We have been mostly contacting each other via Teams conversation. 

 

See you next time!

 

-KBD 💙


********************************************************************************

We got feedback from the course personnel about this post regarding the specification of the regulators. 

Regulators referred in this case are authorities such as GDPR since there will be information for example about the employees saved to the platform.

********************************************************************************


References in this post:

 

Mind Tools. (2021). Stakeholder Analysis. Available (accessed 3.2.2021): https://www.mindtools.com/pages/article/newPPM_07.htm.

 

Koski, L. (2015). Business Model Canvasin soveltuvuus liiketoiminnan suunnitteluvaiheessa. Faculty of Business and Built Environment, Thesis. Available (accessed 11.2.2021): https://trepo.tuni.fi/bitstream/handle/123456789/22728/Koski.pdf?sequence=3&isAllowed=y.

 

Kommentit

Tämän blogin suosituimmat tekstit

Future technology focused possibilities considering our solution

Knowledge Boosting Diamonds Team Introduction