Jeff Lash

Like, OK, you told me what's going on.

But when you explain the why, then I'll then I'll understand, you know, you're not talking about the fact that like, oh, you wear glasses and so you need a higher contrast or you need a higher font size.

No, you literally mean I cannot access the computer to access your website.

It's literally a roadblock to me.

That's a great story.

Yeah, so I think, you know, I think the artifacts are always helpful.

I mean, you know, and in fact, I will also say lack of artifacts is also helpful, right?

I've been in a lot of situations where I asked to say, hey, can you show me a roadmap requirements, business case, product overview, whatever.

And that doesn't exist or it exists in pieces.

And the fact that

it exists in someone's head or it exists in 10 different places scattered across the organization, that also is informative, right?

It tells me like, oh, okay, so this stuff is not documented.

There's not a consistent process.

There's no one reviewing these.

Maybe other stakeholders aren't aware of these things.

So it's not that those artifacts are necessarily good or bad.

It's just, I don't view it as a binary, yes, you have it, no, you don't, thumbs up, thumbs down situation.

Yeah, that's really interesting.

Talking about the whole idea of having these answers and listening and joining new companies, especially today, unfortunately, there's a lot of people joining new companies all the time.

What advice would you say, you know, in someone's first 30 or 60 days at a new company, especially if they're in a leadership role, they're expected to come in and just have answers right away.