Short answer: Wiley Jones shows Doss bot describing how SKUs connect to sales channels and order workflows, including ShipStation labels, by reading its own implementation. Jordan Metzner calls it exposing tribal knowledge.
From Episode 44: This AI Platform Lets Anyone in Your Company Manage Operations Without a Single Engineer, starting at 15:44.
Wiley Jones [15:43]: Yeah. So just super quick because I took a minute to run, asking you to make a shorter description of this. But it actually is able to describe here not just like a, tell me how my orders are doing, but it actually is able to self introspect and say, here's how your product catalog connects to your SKUs and how your SKUs connect to your sales channels and how we process different orders across different channels and actually how our order processing workflow works all the way from sales order to scanning and leaving the warehouse. And it's like, line by line in here and we can actually go in and look very specifically at the workflows that drive this. We can see in here for third party shipping, they're using ShipStation to go and actually purchase the shipping labels. We're actually generating dummy labels to then for pickup and local delivery because they don't actually have to pay for the shipping label but they wanna put something on it so people know who it's going to. Transfer orders, things like that, same such situation. So very, very detailed precise understanding of the system behavior and it's not reading documentation. It's actually reading its own implementation. So that's one thing that's really unique and possible as a result of the architecture of the product.
Jordan Metzner [16:50]: That's great. So this is, essentially tribal knowledge for lack of a better term. Right? Like, maybe somebody knows all of this, but probably a lot of people know pieces of this, but maybe nobody knows all of this altogether or maybe one or two do. And this is kind of exposing that tribal knowledge in a transparent format.
Wiley Jones [17:04]: It's tribal knowledge but it's also implicit. I would say system behaviors that are made to be explicit. So a common way of describing this is if you were to ask someone who has used I don't know. Like if you've ever used any social media product and you ask people, how do you go post on Twitter or how do you go post a photo on Instagram? Well, they would say, I go hit the button, I hit post and then I can actually go and hit like and I can take all these actions and if I hit delete then it'll delete it? You know how the system works and how the system functions. You have a kind of a mental model of the life cycle of how a post works or how, liking and commenting works. The complexity of what I just showed on here is much more complex than like the simple understanding of I post a picture, it shows up in some speed. And so it allows us to take complex rich workflows and data models and represent them in a manner that's legible so that people don't have to just remember how the thing works. It's it's less tribal knowledge in how does our company handle x y z process and it's more taking implicit system behavior and making it explicit.
Jordan Metzner [18:11]: That's great. Awesome demo too. Awesome. Great job. Thanks, Wiley, so much. Alright, Sam. Let's jump into the news.