 So what are roadmaps? We have a talk on this more from a conversations at Lab Week and our Endress Summit. Actually, if Juan here, if you want to talk through this, you did a really great presentation on it. This is me grabbing your slides, but I can voice over. Yeah, happy to. The thing you hear is that when you think about roadmaps, there are several different levels which you might think about describing a roadmap for a team or a project. There's, of course, the lowest zoom level might be a very detailed set of tasks and to-dos that you and your team are directly executing on. And then when you can sort of zoom out from that and you start thinking about the milestones that you're working with other teams in adjacent areas with, you look at a higher granularity, then you can zoom out at an even higher level and then start looking at a set of specific milestones that then maybe consumers of your project or other groups that are further away from your work but are dependent upon your work, the information about it and so on. So as you're thinking about updating and describing progress along a vision or progress along a trajectory for a project, it's extremely useful to have these different roadmaps, different levels of granularity for the different groups that need access to this information. So we've done pretty well in terms of figuring out kind of the lower granularity roadmaps and various different teams use different tools, everything from GitHub to Gantt charts to their own tasks and to-do list and whatnot. And what we were missing was this kind of like higher level zoom view, what here in the slide is described as kind of like zoom level three in a sense that corresponds well to the kind of roadmaps that a number of teams have been working on in the last couple of quarters in terms of having kind of a road map on the earth with masses in the order of like three to six mass stones spanning somewhere between you know kind of two to six quarters ahead in time. These are not kind of like very prescriptive boundaries but they kind of give you a sense of roughly the set of masses that you want to be able to communicate to a larger set of users that kind of wouldn't know the progress on the project. So that's the set of roadmaps that we're using to coordinate across all of our teams and with a lot of the dependent users that's kind of like that's in level three set of roadmaps and that's what's kind of going to start maps and which Molly has been using in the core improvement road map slides. Like those are kind of like that's in level three. Exactly. And I think that was my next slide as well. Like probably the biggest thing having read through everyone's roadmaps over the past couple of days since we landed first drafts of those earlier this week is we've tended to do too many. Is your biggest takeaway is focus, focus, focus. You can have more milestones that you keep track of as your team, as what you're working on. But when you visualize a user focused roadmap, this is like five milestones a year. If you have five themes per year each of which has five milestones, you're doing it wrong. That's too many milestones. Those are not user focused milestones. Those are maybe team development milestones. And so focus your roadmaps come up and the wonderful thing is this is now computable. It's in tools, it's in GitHub issues. You can have many issues and you can have different views that you include some children in one view but not another view. And so big thanks to this new computable tool which is more machine readable, interlinkable and automates that visualization process. You actually get much more optionality on how you wanna visualize things which I think is really exciting. Yeah, roughly the milestone count here will depend by project like you, it's not exactly five persons like that. It's kind of like a think of it as a range but definitely like if you're giving people more than six things to care about like you're already kind of past the point of them being able to remember and so on. So really think of the Zoom level three as communicating to thousands, to tens of thousands of people, not a very granular thing. What most team members individually will care about in your team is the lower level, lower granularity maps. So kind of with Zoom level one and two. Julie, I don't know if you want to talk us really quickly through star maps, the two of it. Yeah, exactly. So I think a lot was already said so I'll skip over some things. But yeah, most if not all of Endra's teams have now added their roadmaps to GitHub. So a huge thank you there and huge thank you to everyone who's offered feedback along the way. For the time being you can find those links in Notion and we'll probably figure out a better home for those. But yeah, all the links that you see in the link there are compatible with star maps. So feel free to play around and explore some other team roadmaps. So just quickly, this is what you would see if you pasted a roadmap link in star maps. This one is actually a rendering of roadmaps across all of Endra's in the detailed view which is what you're looking at. You can see that top level issue and then a milestone one level down. If that milestone has child milestones you can keep clicking into that so you get more and more granular as you go. Each one as Molly mentioned has a link to GitHub so you can follow along the issue there. And then also as those child milestone issues close in GitHub, you'll start to see a progress indicator which we're not seeing on this one yet, but we will soon. It is working though. So if you do have any closed issues you'll see it for your roadmap. But yeah, I'm intentionally not going into too much detail that's the gist of it. I would love though folks to play around and offer any feedback that they have so that we can help make this tool super user friendly and great for the work. Thank you so much for building this. Yeah, I grabbed this together from all of the different roadmaps. I think there is some already immediate learnings from going through that exercise. I created like six new route issues last night with different visualizations of sub milestones. Like definitely learnings around if you break things up into a lot of different themes, hard to see what are the major milestones that are happening within there. All you get is the theme, not the milestone. And also if you don't put any ETAs in your root issue then that gives us warnings and concerns. And so always put an ETA and just do your best estimate for what's contained within the roadmap that's being described there. But I definitely think this gives us a highly flexible tool. We're gonna keep iterating on it. But the really cool thing that this is not unlocks, again, all of these issues are happening in each team's specific repo in GitHub where they are tracking kind of their roadmap areas. Many different people own these different issues and can make their own views. If you have other ecosystems in, you know, say the Olympia to Peace space or IPFS where many different teams across implementations like IRO and other groups are building capabilities that create cross dependencies or should live in an overall IPFS project roadmap or Falcon project roadmap that extends across multiple groups, we can create visualizations across the roadmaps of all of those different teams and communities. It's truly open source and cross ecosystem and network native in how it can visualize the contributions that are happening across many different teams. So we do not see this as the thing just for Endress. We are biting the bullet of helping build the tool and be early guinea pig testers of putting our roadmaps in it. But we would love to see this become more new and a tool that is super valuable across the whole PL network. But we still have some work to do to get it to that point. And one thing you'll notice as we start using these is that we'll start seeing that some of the milestones won't line up, meaning some dependencies will like strike out as, hey, wait, suddenly these milestones won't actually be possible. And yeah, this is exactly what we hope will pop out of a lot of this stuff. So a lot of the, these are the first integration of everybody's individual roadmaps. It'll take a while while we sort through that and detangle some of the dependencies. And I think right now we don't have, we have children, but we don't have dependencies yet between different areas. And so that's a future thing for us to be able to define those dependencies and make things turn red if the timeline of a dependency is after the timeline of a thing that is dependent on it. Great, that gives us good signals. And we can use these visualization tools to alert us and then drill down within these areas. And so that is, this is the wonderful tool, StarMaps. You can open items in GitHub. You can swap into a more detailed view that sees kind of the sub items within different themes. All sorts of really, really cool stuff. It's a big, big thanks to the Ignite team for building this. Please keep giving them lots of feedback as GitHub issues on the StarMaps repo. And yeah, we're gonna keep moving forward on it.