Ecosystem Mapping — How and Why With Canux Founder Cornelius Rachieru
@tags:: #lit✍/🎧podcast/highlights
@links::
@ref:: Ecosystem Mapping — How and Why With Canux Founder Cornelius Rachieru
@author:: Rosenfeld Review Podcast
=this.file.name
Reference
=this.ref
Notes
(highlight:: The Different Levels of Design: Feature, Artifact, Service, and Ecosystem Level
Summary:
A designer develops features for digital services or products using basic IAs, wireframing, prototyping, and usability testing.
Moving up to the product level involves more advanced concepts like journey mapping and site mapping. The service level involves a collection of services and products working together.
The ecosystem level encompasses services working together at a business level.
Beyond that is the universal level, which applies to humanity as a whole.
Transcript:
Speaker 1
So I kind of look at things as we have a feature level or artifact level. So this is when a designer is asked to develop a certain feature for either a digital service or a product or whatever. So it's very contained. Typically a designer would use some basic IAs, some wireframing, some quick prototyping and then would do some usability testing. Of course, all baked in with research. So this is the typical junior designer coming in out of school with the basic knowledge that you get through school training and then you can actually be productive. Then you move up to the product level. So this is where more advanced IAs concepts come in, but still the typical wireframing prototyping. This is where journey mapping comes in a little bit. This is where site mapping comes in. So this is where people can actually look at a higher, just a higher zoom level than the feature and the artifact level. Then there's the service level. So I think of it as a collection of services and a collection of products or a collection of people that try to do something together and it's not a single product or single artifact that We're talking about. And then there's the ecosystem. So this is a collection of services that work together in order to provide typically at a business level results. And it's funny enough that you mentioned the universe because I also think that there's a higher level of this called the universal level. And there are, I was thinking about mapping the ecosystem the way I look at it, mapping ecosystem at the scale of a Facebook or a Microsoft or any sort of major both software and hardware Provider. And those companies that are ubiquitous, I think are above the ecosystem level. I think the ecosystem that I'm at is still too zoomed in compared to the scale that they do business at. I think there's a universal level above that that's more applicable to the humanity as a whole.)
- Time 0:04:59
-
(highlight:: What is Service Ecosystem Mapping in a Business Context?
Summary:
Ecosystem mapping is a collaborative process that helps companies visualize and understand the services and relationships within their operating space.
It is a strategic tool for anticipating business needs and determining the direction to go.
Transcript:
Speaker 1
I think of ecosystem mapping more or less as a collaborative process that helps companies visualize and at the same time understand the services and the relationship between the services Within the space that they or the ecosystem that they operate in. So that is to me the base layer of the type of ecosystem mapping that I do. And that's why I call it service ecosystem mapping. And I don't just call it like product ecosystem mapping or device ecosystem mapping or platform ecosystem mapping because these are things that people have already sort of mentioned And referenced before. But I don't think they are quite adept at solving the kind of problems that for example, business executives are trying to solve when they're looking forward into, you know, being able To anticipate business needs and anticipate direction for where they need to go. So I think of it as a strategic tool rather than sort of hands on design delivery type tool.)
- Time 0:07:41
-
dg-publish: true
created: 2024-07-01
modified: 2024-07-01
title: Ecosystem Mapping — How and Why With Canux Founder Cornelius Rachieru
source: snipd
@tags:: #lit✍/🎧podcast/highlights
@links::
@ref:: Ecosystem Mapping — How and Why With Canux Founder Cornelius Rachieru
@author:: Rosenfeld Review Podcast
=this.file.name
Reference
=this.ref
Notes
(highlight:: The Different Levels of Design: Feature, Artifact, Service, and Ecosystem Level
Summary:
A designer develops features for digital services or products using basic IAs, wireframing, prototyping, and usability testing.
Moving up to the product level involves more advanced concepts like journey mapping and site mapping. The service level involves a collection of services and products working together.
The ecosystem level encompasses services working together at a business level.
Beyond that is the universal level, which applies to humanity as a whole.
Transcript:
Speaker 1
So I kind of look at things as we have a feature level or artifact level. So this is when a designer is asked to develop a certain feature for either a digital service or a product or whatever. So it's very contained. Typically a designer would use some basic IAs, some wireframing, some quick prototyping and then would do some usability testing. Of course, all baked in with research. So this is the typical junior designer coming in out of school with the basic knowledge that you get through school training and then you can actually be productive. Then you move up to the product level. So this is where more advanced IAs concepts come in, but still the typical wireframing prototyping. This is where journey mapping comes in a little bit. This is where site mapping comes in. So this is where people can actually look at a higher, just a higher zoom level than the feature and the artifact level. Then there's the service level. So I think of it as a collection of services and a collection of products or a collection of people that try to do something together and it's not a single product or single artifact that We're talking about. And then there's the ecosystem. So this is a collection of services that work together in order to provide typically at a business level results. And it's funny enough that you mentioned the universe because I also think that there's a higher level of this called the universal level. And there are, I was thinking about mapping the ecosystem the way I look at it, mapping ecosystem at the scale of a Facebook or a Microsoft or any sort of major both software and hardware Provider. And those companies that are ubiquitous, I think are above the ecosystem level. I think the ecosystem that I'm at is still too zoomed in compared to the scale that they do business at. I think there's a universal level above that that's more applicable to the humanity as a whole.)
- Time 0:04:59
-
(highlight:: What is Service Ecosystem Mapping in a Business Context?
Summary:
Ecosystem mapping is a collaborative process that helps companies visualize and understand the services and relationships within their operating space.
It is a strategic tool for anticipating business needs and determining the direction to go.
Transcript:
Speaker 1
I think of ecosystem mapping more or less as a collaborative process that helps companies visualize and at the same time understand the services and the relationship between the services Within the space that they or the ecosystem that they operate in. So that is to me the base layer of the type of ecosystem mapping that I do. And that's why I call it service ecosystem mapping. And I don't just call it like product ecosystem mapping or device ecosystem mapping or platform ecosystem mapping because these are things that people have already sort of mentioned And referenced before. But I don't think they are quite adept at solving the kind of problems that for example, business executives are trying to solve when they're looking forward into, you know, being able To anticipate business needs and anticipate direction for where they need to go. So I think of it as a strategic tool rather than sort of hands on design delivery type tool.)
- Time 0:07:41
-