Jeremy Henrickson: evaluation

Transcript context

…... country. That's right, went all the way to ground. It's like, okay, let's go and open up the big old, I mean, it's online these days, the big old textbook and look like it's, or you're in the United States, it's like you have to go look at Ohio or Pennsylvania, which have all these little local city or county based taxes. And it's incredibly instructive to look at just a few of those and think, wow, how do I think about configuring these change unannounced? Some city administrator or the city legislature, whatever they call them, they decide to change the tax rate. Well, how are we going to know about that? How are we going to change it? How are we going to change it so it's effective at the right time? And you don't think about those things until you've gone all the way to ground and looked at how these things are actually worked, how they're communicated, and how they're thought through. And I think the same thing is true of every aspect of every product in different ways. Right? It might be a technical thing, it might be a design thing, it might be a compliance or a regulatory or a governmental thing, but whatever it is, that detail always exists. And unless you're getting down there and seeing it and understanding it firsthand, you don't really understand what your product needs to do. And I think an important element of this that's between the lines maybe is don't delegate this to someone. You may have a tax expert on the team, and I imagine many leaders would be like, go figure this out and tell me. And I think what you're saying is you go do that and learn, become the world expert at it.…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.