رونوشت 🔗
WEBVTT
00:00:00.049 --> 00:00:01.308
Om, I don't know how to say this.
00:00:01.338 --> 00:00:02.269
I'm just gonna say it.
00:00:02.318 --> 00:00:04.929
Solution architects, all the ones that I've worked with anyway.
00:00:05.408 --> 00:00:06.128
But wow.
00:00:06.128 --> 00:00:07.089
They're, they're useless.
00:00:07.120 --> 00:00:08.439
Like they, I sorry.
00:00:08.855 --> 00:00:10.750
I was, I was trying not to say Okay.
00:00:10.849 --> 00:00:12.289
I mean, they live in the ivory tower.
00:00:12.289 --> 00:00:16.250
They make you kiss the ring when you want to make a change, it affects more than one team,
00:00:16.298 --> 00:00:16.568
yeah.
00:00:16.568 --> 00:00:19.390
What I'm hearing you say is they're as useful as doorknobs on a wall.
00:00:19.539 --> 00:00:19.809
Okay.
00:00:19.809 --> 00:00:20.318
That's fine.
00:00:20.388 --> 00:00:21.949
Let's start with that opening.
00:00:22.259 --> 00:00:23.818
Although I have to say.
00:00:23.969 --> 00:00:29.879
in my career, I've only come across one solution architect who actually was worth his soul.
00:00:30.030 --> 00:00:31.109
This guy really got
00:00:31.160 --> 00:00:33.698
Oh, so are you arguing the diamond in the rough argument?
00:00:33.698 --> 00:00:35.079
Is that what Yeah, definitely.
00:00:35.259 --> 00:00:35.738
Oh boy.
00:00:35.798 --> 00:00:35.859
Okay.
00:00:35.859 --> 00:00:36.499
Rough seas.
00:00:36.518 --> 00:00:36.529
Yeah.
00:00:36.529 --> 00:00:37.509
Well, so yeah.
00:00:37.560 --> 00:00:38.700
Well, we're doing it right today.
00:00:39.000 --> 00:00:39.509
Let's do it
00:00:43.243 --> 00:00:44.262
Welcome back to Arguing Agile.
00:00:44.262 --> 00:00:46.122
If this is your first time, I'm Brian Orlando.
00:00:46.323 --> 00:00:47.612
Product manager extraordinaire.
00:00:47.661 --> 00:00:53.031
and this is my co-host, Mr. Om Patel and Enterprise Business Agility Coach to the starts, Mr. Om Patel.
00:00:53.332 --> 00:00:54.201
Welcome.
00:00:54.322 --> 00:00:56.203
It's great to be part of this discussion today.
00:00:56.203 --> 00:01:06.793
we got a comment talking about the relationship between product managers and solution architects, why do product managers and solution architects seem to be at war when they should be partners?
00:01:07.441 --> 00:01:17.733
You're telling me the one person whose literal job is to prevent your product team from building technical debt monsters is the problem
00:01:17.882 --> 00:01:21.212
I can't even with you can't, like we both can't be sassy for this podcast.
00:01:21.212 --> 00:01:22.503
No, we can't, but okay.
00:01:22.503 --> 00:01:22.983
We can try.
00:01:23.082 --> 00:01:33.921
So, yeah, that brings us to the topic of this podcast the only reason that product managers and architects slash solution architects clash is because the architect role it's not a real role.
00:01:34.322 --> 00:01:40.632
Anybody that's on the internet crying about how Scrum as is not a real job, that I feel the same way about solution architects.
00:01:40.662 --> 00:01:41.561
Let's argue about it.
00:01:41.701 --> 00:01:42.302
Awesome.
00:01:42.391 --> 00:01:43.262
Well, challenge accepted.
00:01:43.311 --> 00:01:45.412
These are the three things that you're gonna walk away with.
00:01:45.462 --> 00:01:51.251
You're gonna know why PMs and solution architects clash and probably other positions too.
00:01:51.352 --> 00:01:56.052
You're gonna we're gonna talk about three conversations that you can use to try to fix the relationship.
00:01:56.231 --> 00:01:59.022
You notice I said try to, because again, it's not a real position.
00:01:59.022 --> 00:02:08.592
So I don't know if you're gonna be able to, and then we're gonna give you some tips on how to spot gatekeeping versus actual enabling behavior that helps your teams.
00:02:08.842 --> 00:02:14.632
That's supposed to be the benefit of having a solution architect is they can go across teams, they can help enable your teams.
00:02:15.081 --> 00:02:15.442
Right.
00:02:15.491 --> 00:02:18.771
If like we're looking at team topologies they're supposed to be able to enable your teams.
00:02:18.831 --> 00:02:21.412
So that's, that's hopefully what people will get outta the podcast.
00:02:21.831 --> 00:02:22.072
Yeah.
00:02:22.342 --> 00:02:25.192
Maybe we'll leave you a phone number to call Ghostbusters.
00:02:25.461 --> 00:02:26.062
Or somebody.
00:02:26.241 --> 00:02:29.211
Or somebody call Tyrone some, somebody You better call somebody, is what I'm saying.
00:02:29.662 --> 00:02:30.741
The first category here.
00:02:31.266 --> 00:02:34.277
Is why, why does this role even exist?
00:02:34.426 --> 00:02:34.758
Right?
00:02:35.026 --> 00:02:35.236
Yeah.
00:02:35.236 --> 00:02:38.627
Maybe we could just start by defining some of these titles, perhaps, right.
00:02:38.627 --> 00:02:41.986
Solution Architect or enterprise Architect, et cetera.
00:02:42.042 --> 00:02:42.782
Who are these people?
00:02:42.831 --> 00:02:44.812
And how do they wind up in those roles?
00:02:45.002 --> 00:02:50.592
Solution Architect me is somebody who has performed the duties of a technical lead for some time.
00:02:50.592 --> 00:02:57.603
And they finagle their way into a realm in the organization where they're hands off basically.
00:02:57.703 --> 00:02:58.812
In large organizations.
00:02:58.812 --> 00:03:04.332
I get that you may actually have like an enterprise architecture board or something like that.
00:03:04.383 --> 00:03:06.122
And these are active members, right?
00:03:06.212 --> 00:03:10.383
Real card carrying members of that, of that guild, if you will.
00:03:10.633 --> 00:03:12.402
Technical architect, solution architect.
00:03:12.402 --> 00:03:13.182
There's a bunch of name.
00:03:13.242 --> 00:03:19.923
Again, another reason why this is, it's made up like there, do you like my new sassiness level on the podcast?
00:03:19.923 --> 00:03:26.212
Let's kick into the steelman to talk about the steelman points here are, they're pretty good.
00:03:26.263 -->
Load full transcript
00:03:33.282
Two bullet points that especially for large organizations, they make a big impact and we will address each one of them, right?
00:03:33.522 --> 00:03:37.932
Number one, like someone's gotta prevent the teams from creating incompatible systems.
00:03:38.052 --> 00:03:45.103
Or team A is trying to solve a messaging problem, so they like go spin up an entire Reds implementation and architecture or whatever.
00:03:45.103 --> 00:03:46.902
And then Team B is just using a database.
00:03:47.052 --> 00:03:52.552
I think about like horror stories from like the old Twitter world where people didn't talk to each other like somebody.
00:03:52.598 --> 00:03:56.198
It needs to have the final call or at least some sort of oversight.
00:03:56.198 --> 00:03:59.198
Or like in larger organizations, you would say governance.
00:03:59.198 --> 00:04:00.907
That would be the dirty word you would use.
00:04:00.957 --> 00:04:08.647
And then the other one is the product managers here, most of them, they're on LinkedIn posting selfies, trying to make sure their hair looks perfect or whatever.
00:04:08.647 --> 00:04:21.288
They don't have the deep technical chops to understand what your teams are about to do, so you need someone to be the quote glue between teams to help them.
00:04:21.288 --> 00:04:22.338
That's the Steelman case.
00:04:22.338 --> 00:04:24.987
And I feel that's a pretty strong Steelman case in this sense.
00:04:24.987 --> 00:04:31.327
I think there's a slight distinction there between technical architects or solution architects versus enterprise architects.
00:04:31.447 --> 00:04:36.028
So at the team level, you could go ahead and weave out a solution that your team needs, that's fine.
00:04:36.358 --> 00:04:40.978
But at an enterprise level, are you creating duplicate solutions?
00:04:40.978 --> 00:04:42.658
Solutions that compete with one another?
00:04:42.658 --> 00:04:43.017
Right.
00:04:43.072 --> 00:05:01.682
. So those things, solutions are, to your point, not compatible but also if you go back to the team level, at a lower level than just the enterprise, we need to ensure that the solutions that are being created at each of these levels can scale up and perform the duties that they're designed for.
00:05:01.687 --> 00:05:17.612
Yeah so this might be a role for somebody like this person that we're, we're describing a solutions architect To figure out, you know is this solution compatible with what we're doing as a direction with our enterprise?
00:05:18.023 --> 00:05:20.843
Strong steelman points in this category.
00:05:20.872 --> 00:05:21.773
I definitely agree.
00:05:21.923 --> 00:05:28.593
However if I'm gonna push back, I'm gonna say again, this role, like everyone crying about Scrum Masters, same thing with this role.
00:05:28.642 --> 00:05:30.833
it exists because you've got gaps.
00:05:30.952 --> 00:05:35.697
Like you never read Team topologies by Manuel Pius and the other guy, Matthew Skeleton.
00:05:35.737 --> 00:05:37.148
And
you never listen to arguing.
00:05:37.148 --> 00:05:37.447
Agile.
00:05:37.447 --> 00:05:39.057
67 team topologies.
00:05:39.278 --> 00:05:45.658
Organizing business and technology teams for fast flow from June 24th, 2022.
00:05:45.848 --> 00:05:46.262
Up people.
00:05:46.843 --> 00:05:48.608
By the way, that was a long time ago.
00:05:48.612 --> 00:05:53.593
Three years ago, that podcast was formed and we taught you all about team topologies and different types of teams.
00:05:53.742 --> 00:06:01.132
Well your organization and your tech leads and your CTOs and whatever, they never read the book and didn't, first of all, that's what I'm saying.
00:06:01.163 --> 00:06:04.463
They're not looking for help, nor is it being accepted.
00:06:05.033 --> 00:06:08.302
And you have this position because.
00:06:08.632 --> 00:06:18.213
They couldn't just read a book that says like, oh, well your team should talk to each other, and if they're not, you should make them intersect on these lines and think about using org design to help you punch head.
00:06:18.283 --> 00:06:21.012
In lieu of doing a bunch of hard work on 'em, that's what I'm saying.
00:06:21.043 --> 00:06:21.312
Yeah.
00:06:21.562 --> 00:06:26.872
They created this position and just, they're just shucking it off this position, be like, Hey, get in there kid.
00:06:26.903 --> 00:06:27.653
Figure it out.
00:06:27.653 --> 00:06:28.913
that's what this position is.
00:06:28.973 --> 00:06:34.257
And of course, like the person that has a huge ego is like, well, I'm tapped by management to figure it out.
00:06:34.312 --> 00:06:41.702
So you gotta invite me to all your daily standups and you gotta invite me to all your planning meetings and you know, I'm gonna be the hippo in the room basically.
00:06:41.733 --> 00:06:44.523
'cause I got a director title or whatever VP title, whatever it is.
00:06:45.103 --> 00:06:46.663
Somebody with a budget is what I'm saying.
00:06:46.783 --> 00:06:54.463
They just pulled out of the air, oh, I'm gonna invent this new position and throw it at the problem rather than actually solving the problem.
00:06:54.523 --> 00:06:54.793
Yeah.
00:06:54.973 --> 00:06:55.182
Yeah.
00:06:55.182 --> 00:06:58.543
Those executives you know, are getting all the help that they didn't ask for.
00:06:58.663 --> 00:07:01.762
So the number one, that's why they exist.
00:07:01.942 --> 00:07:04.552
I have worked with good architects, right?
00:07:04.642 --> 00:07:06.052
Like, people that span teams.
00:07:06.322 --> 00:07:09.052
They're not dedicated to one team or another, and that's what they do.
00:07:09.052 --> 00:07:13.642
I think about a lot of AWS shops, a lot of people that really know how AWS works.
00:07:13.942 --> 00:07:21.413
So when they come in and a team is like, oh, I don't know about Hmm, we need to implement queuing, but maybe we can use a database table and maybe we can use this, maybe we can use that.
00:07:21.742 --> 00:07:28.603
And this person comes in and says like, well
do you wanna use Redis or Kafka or SQS, or, you know what I mean?
00:07:28.603 --> 00:07:41.413
Like they have a half a dozen solutions that they've worked with in the past, ready and available to suggest to the team and then help the team understand what other teams are doing, right?
00:07:41.413 --> 00:07:46.612
Because they know, 'cause they either, either because of their position or because of their tenure service at the organization.
00:07:46.992 --> 00:07:54.913
And that is that architect level helping, enabling, that's what I think of as a positive in this category.
00:07:55.242 --> 00:07:57.492
The positive folks make a big difference.
00:07:57.492 --> 00:08:06.182
Yeah, the bad architects, they become the bottleneck that the team has to go through for approval and it holds up everything.
00:08:06.182 --> 00:08:25.913
It's like, oh, you can't make any decisions because quote governance says, in order to use the new server or new technology or whatever, you've gotta get the approval of these two people so then everybody down the line, product people, team, senior engineers, everybody says like, well, we're not even gonna consider that because we gotta get approval and we're not even gonna bother that.
00:08:25.913 --> 00:08:26.497
That's what it ends up being.
00:08:26.648 --> 00:08:27.937
All coming from this one person.
00:08:28.038 --> 00:08:38.977
The other one that I have next to you is the bullet point that most architecture decisions are actually team coordination problems in disguise because they have to go through the solution architect.
00:08:39.528 --> 00:08:40.488
That's been my experience.
00:08:40.488 --> 00:08:42.352
I don't know if this lines up with what you've seen.
00:08:42.812 --> 00:08:44.732
I've seen that more often than not.
00:08:44.783 --> 00:08:51.052
Actually I've only ever, I can only recall one experience I've had where the architect was invisible.
00:08:51.113 --> 00:08:51.293
Yeah.
00:08:51.383 --> 00:08:52.582
But behind the scenes.
00:08:52.913 --> 00:08:57.352
They were laying out the architectural runway that made sense.
00:08:57.352 --> 00:08:58.373
Not for the team.
00:08:58.403 --> 00:08:58.523
Mm-hmm.
00:08:58.552 --> 00:09:03.472
I'm talking about for the organization so people are across the aisle weren't Right.
00:09:03.472 --> 00:09:15.712
Like coming up with their own solutions that would probably be incongruent with where the organization's going only come across it one time, folks one time and I've been at this game for a while, so this is actually very true.
00:09:15.923 --> 00:09:19.013
You have architects that really can do this.
00:09:19.072 --> 00:09:19.163
Yeah.
00:09:19.212 --> 00:09:21.403
And they say, well, this is the best thing since sliced bread.
00:09:21.462 --> 00:09:21.552
Yeah.
00:09:21.582 --> 00:09:24.732
I, I use Kafka in my previous life, and that's what we're gonna do here.
00:09:24.763 --> 00:09:25.572
But in reality,
00:09:25.572 --> 00:09:28.842
like you're, you're just, you got a hammer and you're doing every job with a hammer.
00:09:28.842 --> 00:09:29.442
That's what's happening.
00:09:29.447 --> 00:09:30.018
Exactly.
00:09:30.018 --> 00:09:32.268
So maybe, maybe the right solution isn't Kafka.
00:09:32.268 --> 00:09:34.758
Maybe it's like an enterprise messaging bus or whatever it is.
00:09:34.937 --> 00:09:36.107
But, so these people.
00:09:36.408 --> 00:09:38.898
Derail the organization.
00:09:38.903 --> 00:09:44.011
at the risk of trying to get a project done quickly it just depends on where they're reporting into.
00:09:44.221 --> 00:09:51.981
If they're reporting into leadership that they are saying, get this done now, get this done next month they're gonna take the easy way out, right?
00:09:52.201 --> 00:09:53.971
They'll, they take the path of water, right.
00:09:53.971 --> 00:09:56.642
If they're reporting into a enterprise architecture.
00:09:56.942 --> 00:09:58.081
Structure of some kind.
00:09:58.081 --> 00:09:59.282
Usually it's a board.
00:09:59.312 --> 00:10:04.081
That say across the organization, this is the direction we're going in, right.
00:10:04.111 --> 00:10:05.341
This is where we're vested.
00:10:05.682 --> 00:10:06.371
Then great.
00:10:06.432 --> 00:10:08.741
But decisions come slow.
00:10:08.741 --> 00:10:10.986
In that case, you've got all kinds of.
00:10:11.302 --> 00:10:14.902
Reviews and approvals and approvals on approvals, et cetera.
00:10:15.322 --> 00:10:21.246
So I think there's a little bit in the podcast later, that way we could kind of touch on how to expedite that.
00:10:21.246 --> 00:10:26.486
But yeah, I've seen both sides of it, but mainly, I've only seen the one side of it, which is not the good side of it.
00:10:26.937 --> 00:10:32.706
Do you have any stories about when a solution architect either killed or saved a project
00:10:33.346 --> 00:10:34.307
it's that, yeah.
00:10:34.307 --> 00:10:35.897
I have an example of both.
00:10:36.076 --> 00:10:36.226
Oh,
00:10:36.226 --> 00:10:36.496
boy.
00:10:36.547 --> 00:10:40.417
Again, without naming names, I will say, I'll lead with the good first, right?
00:10:40.417 --> 00:10:43.687
Of this one enterprise level architect.
00:10:43.866 --> 00:10:53.466
That wasn't his title by the way, but he could think beyond what the team needed, beyond what the domain needed to the organizational level.
00:10:53.917 --> 00:10:58.027
He took the time to understand organizationally where we're going
00:10:58.267 --> 00:10:58.417
Yeah.
00:10:58.616 --> 00:11:02.397
And to his credit, he came back and said, this is a cul-de-sac.
00:11:02.606 --> 00:11:09.187
We're not pursuing this because, and he approached the CIO with this plan real simple, like one slide deck.
00:11:09.216 --> 00:11:12.937
And he said, if we go down this path, here's what's gonna happen here.
00:11:12.937 --> 00:11:17.037
The alternatives and here's why and the CIO approved it right away.
00:11:17.397 --> 00:11:21.447
So the whole organization pivoted away
from the current.
00:11:21.822 --> 00:11:23.861
Path that they were on for the better.
00:11:23.861 --> 00:11:30.812
I might that it turned out six months later I've come across that, which is somebody who is not only just thinking, well, here's what I'm hired for.
00:11:30.812 --> 00:11:31.741
I'm gonna do just that.
00:11:32.172 --> 00:11:33.701
What was the size of that organization?
00:11:33.701 --> 00:11:34.331
I'm just wondering.
00:11:34.572 --> 00:11:38.052
It was a large organization by any stretch.
00:11:38.272 --> 00:11:44.542
My point is the entire org changed direction because of this one person charting a path forward, right?
00:11:44.772 --> 00:11:46.572
So kudos to them, right?
00:11:46.572 --> 00:11:47.177
For coming up with it.
00:11:47.322 --> 00:11:50.231
Well, he went over and beyond what he was hired to do.
00:11:50.902 --> 00:11:53.272
And I've, that's only happened once in my career.
00:11:53.302 --> 00:11:54.711
Now it's go to the other side.
00:11:55.251 --> 00:11:59.692
People that have throttled projects or programs or initiatives.
00:11:59.991 --> 00:12:06.861
I already alluded to some of that earlier, which is they come from a given background, so they have penchant, is that a French word?
00:12:07.131 --> 00:12:09.562
Tendency to say, listen, this is what works.
00:12:09.562 --> 00:12:10.427
I like this tool.
00:12:10.456 --> 00:12:11.687
We're gonna use this tool, right?
00:12:11.716 --> 00:12:12.527
We need this.
00:12:13.126 --> 00:12:28.351
And somehow they managed to win over their superior to kind of sway the decision their way and make the investment if it's a new thing and, and go down that path only to find just a short time later, relatively speaking, a year or so that they actually are in a cul-de-sac.
00:12:28.351 --> 00:12:28.721
Yeah yeah.
00:12:28.932 --> 00:12:40.011
So I've seen that way more often including in one case where the architect in question, they developed their own solution that they thought could plug into this.
00:12:40.011 --> 00:12:41.392
So here's a new.
00:12:41.991 --> 00:12:47.032
You know, weird shaped Lego brick that I think is gonna plug in very well with the rest of your Lego bricks.
00:12:47.032 --> 00:12:47.121
Yeah.
00:12:47.331 --> 00:12:49.011
And you need mine, right?
00:12:49.351 --> 00:12:51.091
and they entrench themselves that way.
00:12:51.091 --> 00:13:01.032
even though it turns out that's not the best solution for the org, but once you go down that path, once that train, starts rolling, it's hard to pull it back.
00:13:01.542 --> 00:13:05.442
I'm starting to suspect that trains are just bad analogies for software development.
00:13:05.591 --> 00:13:08.081
If you're on an Agile release bus, let us know.
00:13:08.091 --> 00:13:18.392
So if you can't find a spot two weeks out on your solution architect's calendar, that should be a red flag you have a permission slip dispenser as a solution architect, by the way.
00:13:18.812 --> 00:13:20.402
Not, not someone that's
there to help you.
00:13:20.501 --> 00:13:26.001
I could levy the same criticism at product managers so I've got, I've got three takeaways that I wrote down for this.
00:13:26.001 --> 00:13:28.371
One is number one count the meetings.
00:13:28.471 --> 00:13:35.601
How many of them have to do with like, reviewing and approving things versus enabling and teaching and helping and mentoring.
00:13:35.841 --> 00:13:36.201
Right.
00:13:36.562 --> 00:13:44.322
And I think a lot of this can be done you don't need a lot of review sessions with your solution architect if they're built into your backlog refinements.
00:13:44.381 --> 00:13:44.621
Yep.
00:13:45.011 --> 00:13:51.782
You know, if they're, if they're way ahead of the daily hustle and grind, there's no reason for them to be these ticket dispensing machines.
00:13:51.812 --> 00:13:51.961
Yeah.
00:13:52.011 --> 00:13:53.481
like a lot of what my experience.
00:13:53.672 --> 00:13:54.692
. But let's move on.
00:13:54.692 --> 00:13:58.261
So are they creating documentation that teams can self-serve?
00:13:58.841 --> 00:14:00.101
Are they understanding the systems?
00:14:00.101 --> 00:14:01.932
Are they helping everyone understand the systems?
00:14:02.261 --> 00:14:07.211
Or, or again, does everyone have to go back to them for that tribal knowledge?
00:14:07.211 --> 00:14:18.091
My experience has always been they will ship you of a PDF from Enterprise Architect, and it's such a high level PDF that it doesn't make sense at the team level.
00:14:18.091 --> 00:14:19.652
So you say, well, where am I in this?
00:14:19.662 --> 00:14:23.081
I'm this little box over here, so can you expand that out?
00:14:23.081 --> 00:14:24.581
And they go, well, let's talk about
00:14:24.581 --> 00:14:25.152
Let's talk about that.
00:14:25.231 --> 00:14:25.802
Pull meeting together.
00:14:25.802 --> 00:14:27.241
So exactly two weeks out.
00:14:27.751 --> 00:14:28.442
Two weeks out's, right?
00:14:28.442 --> 00:14:31.711
Or more in the meantime, you, whoever, whatever your role is, right?
00:14:31.772 --> 00:14:32.912
You've gotta deliver.
00:14:32.912 --> 00:14:35.221
You've got a team that you're working with day in, day out.
00:14:35.432 --> 00:14:36.331
So there is that.
00:14:36.572 --> 00:14:43.081
But the other side of it is that if you have an organization where these people have a platform, like an enterprise architecture board, yeah.
00:14:43.182 --> 00:14:46.792
Are you invited even on a request basis, right?
00:14:46.792 --> 00:14:49.491
So you don't have to go to every single meeting that they're talking about.
00:14:49.822 --> 00:14:58.761
But when it concerns your area of work, are you invited into that discussion and are you given the ability to unmute and ask questions?
00:14:59.062 --> 00:15:01.761
If you're not, there's something else going on here.
00:15:01.761 --> 00:15:01.912
Yeah.
00:15:02.062 --> 00:15:14.572
So let me maybe like, now it's time for the, this is what I think I heard, What I think I heard was you, you, you ask your developers, what decisions can you and can you not make without the architect?
00:15:14.961 --> 00:15:21.052
Because again, like if, if your architect just like boxes the team in to be like you, you can't make any decisions without me.
00:15:21.591 --> 00:15:25.091
And like at that point do we believe in the lean startup?
00:15:25.451 --> 00:15:27.072
Like, do we believe in what Eric Reese wrote?
00:15:27.072 --> 00:15:29.501
Because at that point you just found a bottleneck.
00:15:29.922 --> 00:15:39.961
And like if we, if we're in bottleneck territory, and I feel at the point where we get into this kind of territory, it's time to start asking, can we fire this person?
00:15:40.277 --> 00:15:51.226
or if we're in this shared services kind of model, can we just not put any money into paying for this person's time and just go hire our own two senior developers on the different teams that can actually talk to each other.
00:15:51.317 --> 00:15:59.417
And then we'll send our developer to your staff meetings or to your developer sync meetings or whatever you have architecture review meetings or whatever you have.
00:15:59.537 --> 00:16:01.427
And then we'll hire two people.
00:16:02.027 --> 00:16:06.616
For the cost of what we pay into a pool of, of a solution architect.
00:16:06.677 --> 00:16:06.856
Right.
00:16:06.856 --> 00:16:10.846
To, to just have somebody do that job for us and, and, and talk to each other in different teams.
00:16:10.996 --> 00:16:19.307
Because everything that we just talked about in this category still I don't see, I don't see how the takeaway here is not like, just talk to each other.
00:16:19.606 --> 00:16:20.596
Yeah, absolutely.
00:16:20.596 --> 00:16:21.976
I mean the symptoms, right?
00:16:21.976 --> 00:16:30.437
So when you're blocked by some sort of decision that the solution architect has to cost, and like you said earlier, the calendar's busy.
00:16:30.437 --> 00:16:30.496
Yeah.
00:16:30.917 --> 00:16:32.626
I mean that, there's that side of it.
00:16:32.626 --> 00:16:38.346
The other side of it is you're not given the autonomy in any way, shape, or form to do even an experiment yeah.
00:16:38.481 --> 00:16:40.822
With something that they haven't blessed.
00:16:41.422 --> 00:16:41.511
Right.
00:16:41.511 --> 00:16:45.532
So they're saying, well, stop do not pass, go, do not collect 200.
00:16:45.831 --> 00:16:48.351
And if you try to do anything, go straight to jail.
00:16:48.351 --> 00:16:50.721
It's like, eh, it's not a good scenario.
00:16:51.152 --> 00:16:53.072
So we've given you a couple things in this category.
00:16:53.072 --> 00:16:59.461
I mean, we could stay on it, probably the whole podcast on category number one, but we're gonna move on because we got places to go.
00:16:59.511 --> 00:17:02.211
Has your experience with this been as painful as mine?
00:17:02.272 --> 00:17:03.621
I would like to know in the comments.
00:17:03.861 --> 00:17:04.761
Let me know, please.
00:17:05.362 --> 00:17:12.491
So in the meanwhile, it wouldn't be fair on the arguing Agile podcast if we didn't ask the question well, who, who owns the technical decisions?
00:17:12.642 --> 00:17:13.751
Maybe the organization.
00:17:14.231 --> 00:17:20.291
Has some real trepidation about putting the final decision in any one person's hands.
00:17:20.291 --> 00:17:24.422
Maybe they've gotten burned before , so what I'm saying is your product manager, they wanna ship fast.
00:17:24.451 --> 00:17:26.281
Your solution architect, they wanna build it, right?
00:17:26.281 --> 00:17:29.711
They wanna build the best version future proof version they can.
00:17:30.071 --> 00:17:33.251
So when those two things conflict, who gets the final?
00:17:33.251 --> 00:17:33.491
Say
00:17:33.791 --> 00:17:35.442
what, what a fantastic point, right?
00:17:35.442 --> 00:17:36.791
Who does get the final say?
00:17:36.791 --> 00:17:46.807
I think in most organizations, unfortunately, under the guise of delivering secure products, or products that scale up and are.
00:17:46.967 --> 00:17:48.017
Robust.
00:17:48.186 --> 00:17:54.696
It's the technical people, the technical architect that gets to really have a say in what's going on.
00:17:55.096 --> 00:18:02.807
The product manager could come back and shout there, still a blue in the face and say, we have to do this because our competitors are doing this, et cetera.
00:18:03.136 --> 00:18:07.037
But it doesn't matter because these people are really the gatekeepers at that point.
00:18:07.136 --> 00:18:08.156
So, yeah, I agree.
00:18:08.156 --> 00:18:21.717
And you know, I think architects they, they love to say, okay, we can't go because, and they'll give you a long list of reasons, well, wouldn't it be better instead to say, well, here the real, maybe here are the reasons, maybe they're right.
00:18:22.136 --> 00:18:23.846
What are we doing to solve those right now?
00:18:23.967 --> 00:18:24.086
Right?
00:18:24.086 --> 00:18:26.396
Because we gotta get to market by a certain date.
00:18:27.037 --> 00:18:27.936
That last piece.
00:18:28.491 --> 00:18:35.432
I, again, in my experience has not been it's not been prevalent, it's not been very forthcoming from these people.
00:18:35.432 --> 00:18:38.461
And they just simply sit back and go, it's gonna take what it's gonna take.
00:18:38.771 --> 00:18:41.021
So your product manager, they want, they wanna ship fast.
00:18:41.231 --> 00:18:46.201
Your solution architect, they want to make sure everything is built right and all the edge cases are taken care of.
00:18:46.241 --> 00:18:50.471
when these two things come into conflict, who gets the final say?
00:18:50.771 --> 00:18:51.971
The final say.
00:18:52.061 --> 00:18:53.352
It's like the final countdown.
00:18:53.396 --> 00:18:54.011
Yeah, yeah, yeah.
00:18:54.011 --> 00:18:55.832
With like, with less keyboards count.
00:18:55.836 --> 00:18:55.957
Yeah.
00:18:56.001 --> 00:19:01.557
So I'm gonna go straight to let's reference the Holy Marty Kagan of Empowered 2020.
00:19:01.856 --> 00:19:03.626
Product managers should own outcomes.
00:19:04.047 --> 00:19:06.237
Engineers own implementation.
00:19:06.237 --> 00:19:09.086
That's what he says in the book, don't throw stones at me.
00:19:09.146 --> 00:19:10.406
That's what Marty Kickin says.
00:19:10.436 --> 00:19:11.396
Go throw stones at him.
00:19:11.696 --> 00:19:18.666
So architects, I think the claim that you can make is architects should enable both and not override either one of those.
00:19:18.866 --> 00:19:24.146
outcomes, implementation, architects should be the bridge between those two things.
00:19:24.446 --> 00:19:28.866
Yeah, I agreed with it and I haven't found a whole lot to kind of disagree with since then.
00:19:29.297 --> 00:19:30.196
So I'm gonna go with that.
00:19:30.257 --> 00:19:31.696
I'm gonna say yes.
00:19:32.106 --> 00:19:34.807
You're going right into the steelman because the steelman is two points.
00:19:34.807 --> 00:19:38.196
So he says architects see across teams.
00:19:38.586 --> 00:19:38.767
Yeah.
00:19:38.826 --> 00:19:41.557
And product managers only deal with their one roadmap or backlog.
00:19:41.856 --> 00:19:48.406
Oh, and also like the technical debt from bad decision , that costs us millions in the long term.
00:19:48.406 --> 00:19:49.991
and also it affects multiple teams.
00:19:50.142 --> 00:19:52.531
So I cannot allow you, Mr. And Mrs.
00:19:52.531 --> 00:20:00.061
Product manager to be making these bad decisions in a vacuum when they are shared components that affect other teams.
00:20:00.571 --> 00:20:01.082
Yeah.
00:20:01.082 --> 00:20:02.221
And I, so, yes, agreed.
00:20:02.261 --> 00:20:02.922
Yeah.
00:20:02.922 --> 00:20:03.311
Yeah, yeah.
00:20:03.311 --> 00:20:06.971
So in this scenario though, offer, what happens is a bit of angst here, right?
00:20:06.971 --> 00:20:10.602
Between the, the, the product management folks and the architects.
00:20:10.606 --> 00:20:18.922
Uhhuh, I think it behooves product management to think about this at a higher level, at the organizational level rather than just but I need this yesterday.
00:20:18.971 --> 00:20:25.082
Yeah, we could do that, but it's gonna come back and bite your product or increment, whatever it is, right.
00:20:25.082 --> 00:20:25.832
At some point.
00:20:26.071 --> 00:20:33.731
A savvy technical architect or a system architect should say I understand the need to get there quick.
00:20:33.811 --> 00:20:42.122
However, we can't do that because we have to build this thing for us as a company, not just you as a product.
00:20:42.182 --> 00:20:46.281
Oh, listen, I'm a hundred percent on board with the pitch that you're making right now,
00:20:46.342 --> 00:20:47.571
but I know it's coming.
00:20:47.571 --> 00:20:48.981
However, oh boy.
00:20:48.981 --> 00:20:59.031
Not to throw stones at product managers on the podcast where I happen to be representing the product manager, but most product managers, they're
just trying to get their roadmap there, deliverable their whatever over the finish line.
00:20:59.481 --> 00:21:01.971
That's not what you just outlined is not their concern.
00:21:01.971 --> 00:21:04.207
I understand, but at what cost so that's the thing.
00:21:04.207 --> 00:21:04.922
Well, they don't know.
00:21:05.011 --> 00:21:07.592
So, so that, that's, I think that's the crux.
00:21:08.041 --> 00:21:08.731
They don't know.
00:21:08.731 --> 00:21:09.676
Or they don't care.
00:21:09.846 --> 00:21:10.412
Or care, yeah.
00:21:10.711 --> 00:21:11.551
We're on the same page.
00:21:11.582 --> 00:21:12.061
They don't care.
00:21:12.061 --> 00:21:14.192
Say, well, this is what I'm hired to do, right?
00:21:14.342 --> 00:21:15.092
So I'm gonna do this.
00:21:15.092 --> 00:21:15.692
Get outta my way.
00:21:15.721 --> 00:21:24.271
I can't tell you how many times I've heard a product manager say like, I can't believe Dome and Team is taking insert time period here to do this quote.
00:21:24.271 --> 00:21:25.922
Simple thing.
00:21:26.521 --> 00:21:31.682
Oh dude, I come across that and whenever that happens, I just say, wow, if you can do this quicker, go for it.
00:21:31.991 --> 00:21:43.852
This is why Solution Architects is like, it's a made up role and it's terrible because again, you could have gone to all the teams that are affected by your changes and if you have to go to eight other teams, maybe that should tell you something about your changes.
00:21:44.642 --> 00:21:51.332
You don't need one person to come down from the mountain with the tablets and be like, these 15 commandments, smack, these 10 commandments.
00:21:51.481 --> 00:21:51.692
You know?
00:21:51.751 --> 00:21:55.662
You don't need one person to do that, just talk to the other teams.
00:21:56.156 --> 00:22:01.106
About how you're gonna screw up their day to day with what you're about to do.
00:22:01.557 --> 00:22:03.836
Our architects love to talk about this technical debt.
00:22:04.287 --> 00:22:16.656
Anything and everything is technical debt to the point where the business no longer even believes technical debt is a thing because they've screamed from the top of the mountain so much and you've eroded even the concept of technical debt
00:22:17.086 --> 00:22:25.696
Well, I think when that happens though, it's the onus is on the architects to be able to explain it to the product folks in ways they understand
00:22:25.696 --> 00:22:26.287
I understand.
00:22:26.406 --> 00:22:34.491
But, most companies you'll never get to that point because there's this contention about where the architects sit organizationally, where the product managers sit organizationally.
00:22:34.731 --> 00:22:43.487
And same thing with the engineers and the product teams and how people are incented it's very complicated, so I have a few points that I wrote down and I wrote these down in a hurry.
00:22:43.487 --> 00:22:45.497
So I don't know if these are the best points.
00:22:45.707 --> 00:22:55.047
'cause the first one is, ownership without authority creates blame without power to change anything, so like that, that's, that's very scary that that bullet point.
00:22:55.497 --> 00:22:55.856
Yeah.
00:22:55.916 --> 00:23:03.926
It's also something that exists pretty much in every organization because authority is not something you are granting to people that need it.
00:23:03.987 --> 00:23:08.757
We're getting in, we're getting into this whole org design and sort of the, the org political.
00:23:09.261 --> 00:23:09.951
Spectrum.
00:23:10.011 --> 00:23:11.481
Well, a discussion here.
00:23:11.481 --> 00:23:23.362
I think it's an org design topic because I think it's an org design podcast because this whole, the whole role is because you've got some issues in your org design.
00:23:23.751 --> 00:23:27.471
If your org design was on point, you wouldn't necessarily need any of these people.
00:23:27.622 --> 00:23:30.951
I mean, maybe you would have an enabling team again.
00:23:30.951 --> 00:23:31.551
Apologies, folks.
00:23:31.612 --> 00:23:32.946
Go read Team Topologies.
00:23:33.096 --> 00:23:40.477
We did a whole podcast on it, arguing Angela 67, it was a long time ago in a galaxy far, far away, but it holds up.
00:23:40.957 --> 00:23:41.227
Okay.
00:23:41.646 --> 00:23:43.207
You got an enabling team.
00:23:43.507 --> 00:23:45.247
That team should be able to come in.
00:23:45.541 --> 00:23:51.182
Supplement your team for a sprint maybe, or a sprint or two or whatever, while we're helping you get the work over the finish line.
00:23:51.392 --> 00:24:00.642
We're here working shoulder to shoulder with you, not coming down from the mountain with some tablets one time inscribed in stone and that's it.
00:24:00.642 --> 00:24:02.652
And we never come back and revisit the plan.
00:24:03.071 --> 00:24:03.132
Yeah.
00:24:03.132 --> 00:24:17.731
And then at the end of the sprint review we come down and say like, stamp a big rejected 'cause you didn't follow my tablets or whatever, that that couldn't foresee X, Y, Z and since your calendar was so busy, I never came back and revisited the decision 'cause there was no opportunity again.
00:24:17.731 --> 00:24:18.721
Like terrible.
00:24:18.721 --> 00:24:26.311
The, the best architects, they coach the teams through making good decisions, architects kind of mentor people more than they coach people to in my opinion that's true.
00:24:26.311 --> 00:24:41.701
but I guess the best ones would have that coaching skill and would be able to help ask questions through like, Hey, why would you use Kafka when we have this fully implemented retic instance and all these other teams are doing it, and.
00:24:42.241 --> 00:24:49.412
It looks like you guys can just slide into the middle of it with very little friction and you know, you just need a key or whatever.
00:24:49.442 --> 00:24:51.501
Yeah oh, we didn't even know we had one of those.
00:24:51.501 --> 00:24:53.781
Oh, well, hey, that's why I'm here.
00:24:54.172 -->
00:24:55.971
Work with me after the call.
00:24:56.182 --> 00:24:57.531
We'll sit down for an hour.
00:24:57.592 --> 00:25:02.832
I'll give you a key, and then you'll be testing it and showing a real demo by the end of the day.
00:25:03.011 --> 00:25:08.692
Oh, I had no idea that was even possible things like that I've seen with good architects.
00:25:09.061 --> 00:25:13.382
Good architects can also not just simply cast decisions and saying, you.
00:25:13.892 --> 00:25:14.251
No.
00:25:14.281 --> 00:25:23.882
Or yes, or you know, well, they really, I mean, I mean they, they, they actually have the ability, right, to speak to, to product and everybody else in the language that they understand.
00:25:23.882 --> 00:25:27.182
And not just like technical architectural jargon.
00:25:27.632 --> 00:25:40.991
So when an architect is basically casting decisions, vetoing, et cetera without the ability to, to explain trade-offs, perhaps if we do this, this will happen or else, right.
00:25:41.231 --> 00:25:42.132
Those sorts of things.
00:25:42.521 --> 00:25:45.251
Are they architecting or are they just simply controlling?
00:25:45.551 --> 00:25:47.412
I think you just answered your own question right there.
00:25:47.412 --> 00:25:47.892
I think I did.
00:25:47.991 --> 00:25:55.412
So I had some time in this category, Stubb Doubt for us to talk about a time where I, as a PM disagreed with an architect.
00:25:55.791 --> 00:26:25.892
And then to talk about who won what shift it would've been, I, I'm, IM trying to remember any conversation that I've had with an architect as a product manager where the architect won because like, this is, again, this is like par partially responsible for my move to product management from working on technical teams where you're just working, the whole team works through the architect, and in poorly organized businesses, the whole technical team works for the architect on paper.
00:26:26.372 --> 00:26:28.201
They have higher fire authority basically.
00:26:28.846 --> 00:26:29.057
Yep.
00:26:29.311 --> 00:26:48.376
Or, or, or at least like they can heavily imply and, and that's not even to mention if you have like a contractor culture where a majority of your people are contractors and then you have this solution architect who's like this VP level person who's like, I don't like this one QA person on this one team because they critiqued my SQS solution.
00:26:48.527 --> 00:26:51.057
They said you should write to SNS.
00:26:51.076 --> 00:26:51.287
Yeah.
00:26:51.346 --> 00:26:54.257
Before it gets pulled into SQS and I don't like that.
00:26:54.416 --> 00:27:01.057
and they can get that person basically fired just because they didn't like getting accused of being wrong basically when they probably were wrong.
00:27:01.176 --> 00:27:01.267
Right.
00:27:01.267 --> 00:27:07.747
Anytime that their authority is challenged, that they feel a bit like vulnerable in that way and they can take it out on the teams.
00:27:07.747 --> 00:27:08.946
But that, those are all my stories.
00:27:08.946 --> 00:27:11.317
I don't, I don't have a great story in this one.
00:27:11.426 --> 00:27:17.967
So I don't know if your architect can say no, but they cannot explain the cost of saying yes.
00:27:18.166 --> 00:27:24.126
Well, look, I think if they can't explain the cost of saying yes, you've got no hope of them explaining the cost of saying no.
00:27:24.426 --> 00:27:30.567
So I mean, at that point they're not really protecting the architecture or looking after that but they're really kind of just.
00:27:30.942 --> 00:27:32.807
Basically gatekeeping.
00:27:32.957 --> 00:27:37.886
I have some quick takeaways in this category, just to throw some out so that we don't just rail in this category.
00:27:37.892 --> 00:27:41.491
I feel it's gonna be that kind of podcast where I rail on every category and it doesn't matter.
00:27:41.731 --> 00:27:44.781
But I'm gonna try to throw some takeaways in there to help people.
00:27:45.301 --> 00:27:48.271
There's three things that I would say that you can try to do.
00:27:48.271 --> 00:27:54.461
You can try to with your architect, you can try to state the customer outcome with them clearly as clearly as you can.
00:27:54.672 --> 00:27:56.291
You should be doing this anyway in primary Yeah.
00:27:56.592 --> 00:27:58.451
To say what, what are we trying to achieve?
00:27:58.961 --> 00:28:09.682
And, and by when, if you like, I under, that's a dirty word to say by when, but maybe there's a market reason or a window or something trying to hit, Just be upfront, be like, Hey, I want to try to do this.
00:28:09.912 --> 00:28:10.511
By this time.
00:28:10.511 --> 00:28:10.811
Okay.
00:28:11.051 --> 00:28:15.071
Number one, just try to get the goal out there and be as clear as possible about it.
00:28:15.541 --> 00:28:26.332
Number two, you wanna try to, to name the technical constraint and why it's risky or not risky just try to work with your person to clearly say, this is what we're trying to do.
00:28:26.392 --> 00:28:34.971
And then to clearly write down, well, these are the constraints because then it opens up the conversation for you to quantify the trade-offs.
00:28:34.971 --> 00:28:40.281
So if we do it, if we rush to market with this, we'll have a bunch of garbage over here.
00:28:40.281 --> 00:28:43.882
We'll have to do a bunch of work or two sprints to clean up whatever, whatever.
00:28:43.882 --> 00:28:45.682
It's, but what is the trade off?
00:28:45.981 --> 00:28:47.932
I might be running my stuff back up the ladder.
00:28:47.932 --> 00:28:48.261
Sure.
00:28:48.352 --> 00:28:53.001
And my director of product and VPs or whatever might be like, we don't care about any of that crap.
00:28:53.491 --> 00:28:56.912
Get us into this new market, ASAP.
00:28:57.132 --> 00:29:02.442
I was at a business one time, had a bunch of technical problems and they were trying to renew a customer.
00:29:02.652 --> 00:29:08.682
And a customer was basically threatening
them, saying, we won't renew unless you make your system quote, quote.
00:29:09.071 --> 00:29:09.882
More stable.
00:29:09.991 --> 00:29:11.491
Which was completely subjective.
00:29:11.491 --> 00:29:14.701
I mean, it basically was like, if we feel it's good, right?
00:29:14.701 --> 00:29:18.362
We'll renew that was like, there's no way you can like run a business off that.
00:29:18.602 --> 00:29:22.951
But at that point, the clock was ticking on the whole technical team.
00:29:23.201 --> 00:29:30.821
It could have sunk the company if a customer that was like over 50% of the revenue for the whole company would've just gone away.
00:29:30.852 --> 00:29:31.122
Yeah.
00:29:31.182 --> 00:29:37.912
It like, there would've been massive layoffs, probably most of which would've been the development team at that point if we couldn't solve it.
00:29:37.951 --> 00:29:43.872
There was none of this like living in the ivory tower letting your hair down like Rapunzel going on at that point.
00:29:43.961 --> 00:29:46.721
It was, everyone needed to work together to solve these issues.
00:29:46.771 --> 00:29:53.991
And then if you're tracking data and you're actually a data-driven organization, you escalate with data, you bring actual data.
00:29:54.291 --> 00:29:59.832
To have conversations with leadership and hopefully you're in the type of organization where you could actually have that kind of
00:29:59.836 --> 00:30:00.017
conversation.
00:30:00.017 --> 00:30:03.612
Yeah, I was gonna say, you, those organizations are also rare, right?
00:30:03.612 --> 00:30:09.672
Because they just simply look at the people underneath and say, you failed, and then they just turn around, look down and say, you failed.
00:30:09.872 --> 00:30:11.642
Those are four takeaways for you.
00:30:12.031 --> 00:30:12.751
One was free.
00:30:13.092 --> 00:30:14.682
We promised three, but we gave you four.
00:30:14.741 --> 00:30:15.011
I know.
00:30:15.011 --> 00:30:15.311
Yeah.
00:30:15.412 --> 00:30:16.811
Hey you know, this is fine.
00:30:16.842 --> 00:30:17.771
This is like that meme.
00:30:17.771 --> 00:30:18.311
This is fine.
00:30:18.317 --> 00:30:18.852
This is all fine.
00:30:18.951 --> 00:30:19.642
This is all good.
00:30:19.971 --> 00:30:21.652
House is burning down around you, but Yeah.
00:30:21.902 --> 00:30:27.261
Hey, what do you think is if you find any of these takeaways useful, let us know in the comments.
00:30:27.892 --> 00:30:30.352
Let's take a different perspective on this arguing point.
00:30:30.531 --> 00:30:34.372
What if product managers, what if they're not innocent in this situation?
00:30:34.372 --> 00:30:36.951
What if, what if a problem is self-created?
00:30:37.132 --> 00:30:39.321
That's the category we're about to go into.
00:30:39.622 --> 00:30:40.221
Wow.
00:30:40.221 --> 00:30:40.612
All right.
00:30:40.612 --> 00:30:42.442
So let's just say for sake of argument Yeah.
00:30:42.501 --> 00:30:48.142
Most of the time when a solution architect becomes a bottleneck mm-hmm.
00:30:48.442 --> 00:30:50.241
It comes down to the product management.
00:30:50.241 --> 00:30:51.771
It's product managers that.
00:30:52.297 --> 00:30:53.406
Cause this to happen.
00:30:53.676 --> 00:30:54.336
How about that?
00:30:54.366 --> 00:31:00.586
Because they're expressing undue, unrealistic deadlines to get out there, right?
00:31:00.586 --> 00:31:01.426
For their own reasons.
00:31:01.606 --> 00:31:03.916
Granted, but maybe that's the case.
00:31:04.396 --> 00:31:05.777
So how how PMs.
00:31:06.152 --> 00:31:10.922
Actually are the root cause of some of these architect issues and problems.
00:31:11.281 --> 00:31:12.932
So I got the steel- man shown on the screen
00:31:12.932 --> 00:31:19.672
product managers are accountable for outcomes, not technical debts that's the steelman argument.
00:31:19.821 --> 00:31:19.882
Yeah.
00:31:19.882 --> 00:31:28.291
And then the second one is, architects should proactively engage and collaborate with product and not wait until they're invited.
00:31:28.682 --> 00:31:31.511
So they are in the game from the beginning, right?
00:31:31.511 --> 00:31:31.602
Mm-hmm.
00:31:32.001 --> 00:31:48.422
If you're in nor where this happens, I would love to know because I've not come across many except for maybe one that was practicing safe as a framework and safe has that element where enterprise architects are part and parcel of the product council.
00:31:48.481 --> 00:31:53.922
So they're up there working with product before they solidify direction for the product.
00:31:54.311 --> 00:31:55.511
That's very, very rare.
00:31:55.571 --> 00:31:59.821
It's academically, yes, that's what you're supposed to do according to the blueprint from safe.
00:31:59.912 --> 00:32:03.602
But in practice, again, not seeing that very often, I'm afraid, folks.
00:32:03.942 --> 00:32:14.356
if I'm going to defend PMs for a second here, I feel, well, boy, I feel slimy defending all PMs right now,, if we're gonna be Rocky, I'm gonna be in their corner with the ice cube thing, the cold thing.
00:32:14.487 --> 00:32:16.346
I'm sure it has a technical name for boxing.
00:32:16.346 --> 00:32:22.416
I have no idea what it's but if I'm gonna be the cold thing, it's like, hey, like sometimes UPMs, like you promise things.
00:32:22.747 --> 00:32:25.176
Without ever engaging the development team.
00:32:25.221 --> 00:32:27.531
Especially if you're with sales and there's no developers there.
00:32:27.582 --> 00:32:28.001
Oh, that'll
00:32:28.001 --> 00:32:32.352
be quick one, sprint boss, whatever you say, we'll have it out in a week.
00:32:32.352 --> 00:32:33.192
We can do that.
00:32:33.551 --> 00:32:34.031
You know what I mean?
00:32:34.031 --> 00:32:35.801
And then your developers are like, what are you talking about?
00:32:35.801 --> 00:32:38.261
This thing's in the middle, in the core of the software.
00:32:38.412 --> 00:32:43.711
Even if we bring developers to that conversation, they could get stuck in the same trap.
00:32:43.711 --> 00:32:48.882
So I feel like a better way is like you involve more people and you get over that hump the more people you involve.
00:32:48.942 --> 00:32:51.011
And now we're back to like, hire your organization.
00:32:51.162 --> 00:32:51.971
and product Right.
00:32:52.031 --> 00:32:53.172
Makes decisions.
00:32:53.672 --> 00:32:54.301
but I don't know.
00:32:54.301 --> 00:32:55.471
That's a weak argument to me.
00:32:55.501 --> 00:33:02.142
'cause also if you go back to that four letter word governance, your solution architect might be like, well, you can't talk to customers without me.
00:33:02.442 --> 00:33:12.061
And because they work for like two levels above your skip level, now it becomes policy that no product teams could talk to any customers without a solution architect in the room.
00:33:12.061 --> 00:33:13.412
And now you're dead.
00:33:13.511 --> 00:33:16.932
These kind of asinine rules become institutionalized Absolutely.
00:33:16.932 --> 00:33:17.501
After a while.
00:33:17.501 --> 00:33:22.971
and that's how we do things here sort of thing and it completely blocks agility.
00:33:23.051 --> 00:33:24.521
These are things I fight day in,
00:33:24.521 --> 00:33:25.961
day out in my day job.
00:33:25.961 --> 00:33:34.067
And, I've seen them across almost every organization at some level with regard to some decision.
00:33:34.067 --> 00:33:37.156
there are certain areas you can press on at certain organizations.
00:33:37.217 --> 00:33:37.457
Yeah.
00:33:37.997 --> 00:33:40.217
And you'll get this.
00:33:40.416 --> 00:33:43.711
The product team can make any decision they want except as long
00:33:43.747 --> 00:33:44.557
as it's not technical,
00:33:44.586 --> 00:33:46.777
except they can't alter pricing.
00:33:47.047 --> 00:33:48.247
Well, yeah, that's right.
00:33:48.507 --> 00:33:52.967
I'm pointing something out that just to be a little over the top to help people understand, . Did
00:33:52.967 --> 00:33:55.067
we do a podcast on who should we doing pricing?
00:33:55.217 --> 00:33:55.781
We certainly did.
00:33:55.781 --> 00:33:55.916
We did, we
00:33:55.916 --> 00:33:56.156
did.
00:33:56.221 --> 00:34:00.156
And I will search for it like it was arguing Agile 236.
00:34:00.176 --> 00:34:12.016
Why product managers should own pricing, not sales or execs or finance We talked about the solution architect being basically the, the chief, no officer, and why that's a problem.
00:34:12.677 --> 00:34:22.806
If, if the PMs are complaining but then treating the the developers on the team or the architects or whoever as like order takers.
00:34:23.106 --> 00:34:26.797
You know, like I think about the, the super high level skip level.
00:34:26.797 --> 00:34:28.416
Like, just get it done.
00:34:28.657 --> 00:34:30.367
I don't care what it takes.
00:34:30.416 --> 00:34:37.706
I think about every executive who's ever said, how hard can it be to just add a little toggle that says light mode, dark mode.
00:34:38.007 --> 00:34:38.817
Oh
my goodness.
00:34:38.817 --> 00:34:40.597
And you have no idea what you're talking about right.
00:34:40.646 --> 00:34:48.246
I think this divide this organizational divide whether it's functional or otherwise, is killing organizations.
00:34:48.246 --> 00:34:55.246
There's gotta be a better way I don't have an answer necessarily, not on this podcast at least, but you know, how about a coalition?
00:34:55.367 --> 00:34:57.556
How about forming a coalition that.
00:34:57.927 --> 00:35:01.797
It's fickle and it, it's unique for every case that you come across.
00:35:01.856 --> 00:35:01.947
Yeah.
00:35:02.056 --> 00:35:07.036
But you bring the right people in for the right amount of time, for the right things and the right reasons.
00:35:07.246 --> 00:35:07.637
And that's it.
00:35:07.637 --> 00:35:10.786
I cut us straight to the actionable takeaway because of your comment there.
00:35:10.936 --> 00:35:11.027
Mm-hmm.
00:35:11.217 --> 00:35:13.277
Which is discovery, not delivery.
00:35:13.277 --> 00:35:14.027
You want to invite them.
00:35:14.027 --> 00:35:16.876
So point number one that's showing on the screen now for you.
00:35:16.967 --> 00:35:17.117
Yeah.
00:35:17.166 --> 00:35:23.317
You want to invite them, the meaning the solution architect, you wanna invite them to discovery through the discovery phase.
00:35:23.347 --> 00:35:23.527
Yeah.
00:35:23.597 --> 00:35:24.467
I'm not gonna go into it.
00:35:24.467 --> 00:35:32.436
We we probably could do a whole podcast just on that phase of the least you can do, I mean, this is the most minimal thing you can do.
00:35:32.797 --> 00:35:33.757
You listen.
00:35:33.786 --> 00:35:35.376
Oh, they never show up to any my things.
00:35:35.376 --> 00:35:36.036
I always invite them.
00:35:36.286 --> 00:35:37.036
Yeah, it is a difference.
00:35:37.036 --> 00:35:38.231
let's, there'll be time.
00:35:38.231 --> 00:35:39.461
They have an accountability there.
00:35:39.521 --> 00:35:41.681
There'll be time in the podcast to talk about that later.
00:35:41.742 --> 00:35:41.952
Yeah.
00:35:42.251 --> 00:35:42.822
About that.
00:35:43.306 --> 00:35:47.746
Accountability, but when we're talking to customers, we've made them available.
00:35:47.927 --> 00:35:49.547
Same thing is like sales.
00:35:49.996 --> 00:35:55.666
When sales is meeting with a prospect and they put me, the product manager on is optional.
00:35:55.967 --> 00:36:02.056
I can choose to not show up to their new sales prospect, but I mean, what, what am I doing that's more important than that?
00:36:02.367 --> 00:36:07.317
I mean, can you talk, do you have the teams and be like, oh, time to sit down and talk technical details, whatever.
00:36:07.317 --> 00:36:08.637
Can you push that back a little?
00:36:08.637 --> 00:36:18.572
Like I know it might impact a daily scrum but I'm like, there should be an order in meetings of like number one, we're talking directly to a customer.
00:36:19.052 --> 00:36:23.791
Number two, we're talking to other teams to
decide something between the two of us.
00:36:24.001 --> 00:36:28.181
Number three, we're just talking internal to the team, number four is a one-on-one or something like that.
00:36:28.181 --> 00:36:31.181
there, there's an order that you can kind of work out.
00:36:31.226 --> 00:36:32.757
, And maybe that's a working agreement.
00:36:32.907 --> 00:36:38.077
Maybe a top level coach can help people understand like hey we can move the meetings.
00:36:38.077 --> 00:36:39.427
There's no cost right.
00:36:39.476 --> 00:36:59.177
I guess this whole diatribe goes back to what is the business context of that thing and did something with a more important business context come up because we should respond to that quickly again, there's a lot of people I even saw like I've been watching a lot of stuff on LinkedIn recently, like crying about Agile and like throwing stones Agile and whatever.
00:36:59.226 --> 00:37:07.387
If we got business agility at the forefront of our minds, we should just know the order instinctually, just know the order and just be like, wow, I'll kick this out.
00:37:07.387 --> 00:37:09.126
I'll make, I'll make time, I'll make time for that.
00:37:09.277 --> 00:37:10.237
That sounds important.
00:37:10.536 --> 00:37:11.436
I know it's important.
00:37:11.527 --> 00:37:12.847
We'll make time to, to get that done.
00:37:13.146 --> 00:37:13.387
Yeah.
00:37:13.387 --> 00:37:14.077
Fully concur.
00:37:14.121 --> 00:37:18.181
I think the order is probably something like prospects that you are farming for first.
00:37:18.402 --> 00:37:20.112
Because why wouldn't you water your seeds?
00:37:20.112 --> 00:37:25.422
You've planted That this makes no sense to me to ignore that customers you've already got, they've signed up.
00:37:25.452 --> 00:37:28.152
Don't ignore 'em, but that's the next level for me.
00:37:28.152 --> 00:37:31.992
and then there's like the organizational looking to your left, looking to your right.
00:37:32.331 --> 00:37:36.532
your team level follows after that what's at the bottom for me is.
00:37:36.996 --> 00:37:42.757
Your EAB, et cetera, because all you're doing is making technical decisions there right now.
00:37:42.817 --> 00:37:47.467
Do you have to make them right now at the expense of those other layers that we just talked about?
00:37:47.976 --> 00:37:49.146
I suspect not, right?
00:37:49.197 --> 00:37:49.286
Yeah.
00:37:49.286 --> 00:37:52.706
Because on the whole you direction isn't gonna change a lot.
00:37:52.706 --> 00:37:52.797
Mm-hmm.
00:37:53.097 --> 00:37:55.527
It's probably small decisions at that point.
00:37:55.876 --> 00:38:02.416
But granted, there are some opportunities where you're talking about larger level discussions on what tool to embrace, et cetera.
00:38:02.416 --> 00:38:04.666
Those are fairly far and few in between.
00:38:04.936 --> 00:38:12.527
So it does make sense and yeah, if your organization doesn't have that kind of a culture, you should work with a coach to, to help instill that.
00:38:12.586 --> 00:38:12.766
Right.
00:38:13.117 --> 00:38:26.356
So my interesting takeaway I'm hearing, as a product manager, if I'm gonna take accountability in this category, if your architect is blocking your roadmap, but they're doing so because it's new to them or you never showed it, or you talk to customers first or whatever.
00:38:26.356 --> 00:38:27.797
You got some explaining to do.
00:38:27.947 --> 00:38:30.646
You're, you're actually precluding a really.
00:38:31.036 --> 00:38:39.746
Important you know, opportunity for your architect to ask questions of your prospects or customers directly, not filter through your lens, right?
00:38:39.746 --> 00:38:42.356
So it's not gonna be something you can talk to them after the fact.
00:38:42.777 --> 00:38:46.376
Like that's better than nothing I guess, but it's not the same, right?
00:38:46.376 --> 00:38:47.996
You need those people in the room.
00:38:48.297 --> 00:38:51.117
So one of the things as a product manager you could do is this.
00:38:51.327 --> 00:38:53.217
You gotta talk to a customer or, or.
00:38:53.802 --> 00:39:06.021
A prospect, doesn't matter which the meeting that is set up, ask the other party the prospect of the customer to bring their architects into the call that way your architect can ask questions and get immediate feedback.
00:39:06.052 --> 00:39:06.172
Mm-hmm.
00:39:06.481 --> 00:39:07.952
'Cause the alternatives are a lot worse.
00:39:08.132 --> 00:39:11.251
Things get filtered and senior develop team leads or whoever it is.
00:39:11.251 --> 00:39:11.972
Yeah, exactly.
00:39:12.152 --> 00:39:24.001
Whoever it is that's needed at this point so I mean, my point on this is, as a product manager, you should definitely be thinking about this and how to short circuit this whole communication conundrum.
00:39:24.661 --> 00:39:26.762
Well, I mean, that's a great wrap for this category.
00:39:26.762 --> 00:39:30.032
Is there any other things that we left out of this category?
00:39:30.632 --> 00:39:32.702
If you're listening, let us know the comments.
00:39:32.731 --> 00:39:33.302
Absolutely.
00:39:33.302 --> 00:39:36.181
We've established that everyone's guilty in this category.
00:39:36.181 --> 00:39:37.262
That's what we've talked about.
00:39:37.862 --> 00:39:46.621
So now let's talk the three conversations that actually can help solve slash fix, maybe the relationship unmuted.
00:39:46.711 --> 00:39:55.411
Alright, so most product manager slash solution architect conflicts, they're not about technical disagreements.
00:39:55.411 --> 00:39:58.771
They are about three conversations that actually never happen.
00:39:59.402 --> 00:40:00.871
That's what the disagreement is about.
00:40:01.021 --> 00:40:12.402
The Patrick Lencioni five Dysfunctions of a Team, the 2002, trust comes from vulnerability based conversations about roles, goals, and fears.
00:40:12.971 --> 00:40:16.150
I'm gonna transition into the Steelman side of this conversation.
00:40:16.201 --> 00:40:22.891
Roles and responsibilities, they should be clearly defined by the organization at each organization that you're at.
00:40:22.891 --> 00:40:34.940
So if you're a product manager at, at Brian and Om software development company , and then you go work for Acme Company or whatever, you should have a conversation with them about exactly how the role is different from the previous.
00:40:35.240 --> 00:40:38.751
Brian o software company where you basically own the entire outcome.
00:40:38.960 --> 00:40:42.650
Everyone basically worked for you, but they didn't really work for you, but you had a, you know what I mean?
00:40:42.655 --> 00:40:42.965
Right.
00:40:42.965 --> 00:40:48.065
And now you're at this new company where everything's like a project plan and you're the king of the world.
00:40:48.146 --> 00:40:53.755
So I think there's two things that fundamentally underlie, rely the ability to be able to do this, right?
00:40:53.760 --> 00:40:53.880
Mm-hmm.
00:40:54.380 --> 00:41:00.536
One is to own the fact that you have to be vulnerable and say let's have a candid conversation.
00:41:00.865 --> 00:41:04.376
That that's one, which again, we know it's not that common, right?
00:41:04.376 --> 00:41:07.286
Because people come in with, this is the second point I wanna make.
00:41:07.556 --> 00:41:07.675
Yeah.
00:41:07.706 --> 00:41:08.396
Egos.
00:41:08.516 --> 00:41:09.925
You gotta check those at the door.
00:41:10.056 --> 00:41:17.786
'Cause I mean, if you, if you come in and say, I'm the the U, but senior product manager, and it's like, yeah, come on seriously.
00:41:18.085 --> 00:41:22.166
So those two things have to be preconditions to this, right?
00:41:22.226 --> 00:41:24.056
Be vulnerable, lose your ego.
00:41:24.106 --> 00:41:28.635
You don't know, but you just hit on a whole different podcast I wanted to have about, Ooh.
00:41:28.666 --> 00:41:29.326
Being humble.
00:41:29.385 --> 00:41:30.795
Being humble.
00:41:30.795 --> 00:41:30.815
Being humble.
00:41:30.856 --> 00:41:31.365
I like it.
00:41:31.425 --> 00:41:31.606
Yeah.
00:41:31.606 --> 00:41:35.516
A lot of people don't, they don't know what being humble means, what does being humble mean?
00:41:36.146 --> 00:41:40.422
Does it mean like, shutting up and like not starting a fight, actually, that's not what it means you know?
00:41:40.422 --> 00:41:45.742
What it, what it means is, bringing up that you disagree with someone and not being a jerk about it.
00:41:46.371 --> 00:41:50.331
Bringing up that you know, you're really worried about someone because of the way they're acting.
00:41:50.362 --> 00:41:53.570
'cause they're a giant alpha type personality.
00:41:53.871 --> 00:42:01.101
And you're concerned about it and you really want to talk to 'em about it to understand why they're that may like maybe something happening at home.
00:42:01.311 --> 00:42:06.831
Maybe they're in a bad place in their life, you don't know, , it's not, you're not trying to win one over on them.
00:42:06.882
--> 00:42:09.612
This is where you come in with your empathy.
00:42:09.851 --> 00:42:15.762
This is where you kind of divulge away a little bit from this ethos of well tackle the problem, not the person.
00:42:15.762 --> 00:42:18.431
Well, look, you have to tackle the problem.
00:42:18.431 --> 00:42:19.001
Sure.
00:42:19.271 --> 00:42:22.391
But it's the people that are going to work on the problems.
00:42:22.452 --> 00:42:30.422
So, to your point, maybe these people that are involved or person that's involved in the picture here has something going on in their personal life.
00:42:30.452 --> 00:42:34.081
It behooves you to at least be open to have that conversation
00:42:34.081 --> 00:42:44.402
The other steelman here is good, good professionals shouldn't need relationship conversations to do their job, which is by the way, terrible, terrible point.
00:42:44.822 --> 00:42:45.992
Hey, you're a professional.
00:42:46.322 --> 00:42:48.632
You should be able to read between the lines zone.
00:42:49.021 --> 00:42:49.442
Yeah.
00:42:49.621 --> 00:42:49.922
Yeah.
00:42:49.927 --> 00:42:58.385
I don't know how I feel about this, because first of all, if this were true, we wouldn't have any problems in the world so let me tackle it the opposite way.
00:42:58.416 --> 00:42:58.445
Okay.
00:42:58.445 --> 00:42:58.626
Alright.
00:42:58.655 --> 00:43:01.467
When do you ever get taught how to do this?
00:43:01.887 --> 00:43:02.217
Right?
00:43:02.246 --> 00:43:03.715
You don't learn this in college?
00:43:03.786 --> 00:43:04.775
Oh, you're a professional.
00:43:04.775 --> 00:43:05.286
No, you're not.
00:43:05.315 --> 00:43:07.655
You learn academic stuff in college.
00:43:07.965 --> 00:43:11.266
So you come to work and where at work do you learn about.
00:43:11.626 --> 00:43:14.101
Being a good professional, you don't.
00:43:14.641 --> 00:43:16.380
So here's how you learn.
00:43:16.650 --> 00:43:18.510
You learn through the school of hard knocks, right?
00:43:18.811 --> 00:43:23.340
So you do something and if it works, you get reinforcement, great.
00:43:23.490 --> 00:43:24.360
You'll do more of it.
00:43:24.570 --> 00:43:27.760
Or you get pointed at for something and you do less of it.
00:43:28.030 --> 00:43:32.411
But then every organizational values, different traits and behaviors and norms, right?
00:43:32.440 --> 00:43:34.601
So how do you get to this point?
00:43:35.030 --> 00:43:35.931
It is not a given.
00:43:35.931 --> 00:43:48.141
It's not, there's nothing wrong with seeking help here, and organizations should be open to saying people that work in our org aren't perfect people, and we should be providing that support that they need.
00:43:48.146 --> 00:43:56.826
so again, as a product manager on the podcast, I would like to take this opportunity to point out that the org chart, defines titles, reporting, structures.
00:43:57.016 --> 00:43:59.115
it never defines how two people.
00:43:59.445 --> 00:44:10.405
Actually collaborate under pressure if you
could redraw your org chart to say, don't show me who reports to who, show me how decisions are actually made in this organization.
00:44:10.405 --> 00:44:13.556
And everyone needs to be involved in all the different tracks.
00:44:13.976 --> 00:44:23.936
First of all, people would be like, get outta my office second of all, I don't even know if they would be able to do that because it's, it's a very complicated thing that I just asked for is show me how decisions.
00:44:24.280 --> 00:44:25.121
Actually get made.
00:44:25.121 --> 00:44:28.570
And maybe, maybe you should do that exercise at your work.
00:44:28.721 --> 00:44:44.971
If I'm wheeling back to another podcast that I want to have, but there's no way to have it without being a completely unhinged I actually did have a conversation in the takeaways and just to throw it out here real quick, the conversation is a three part conversation that I'm suggesting here.
00:44:44.971 --> 00:44:50.561
It says you have a conversation and you ask the question, what does success look like for you in your role?
00:44:50.860 --> 00:44:52.871
And you try to understand their situation.
00:44:52.990 --> 00:45:00.161
So if you're like, oh, I think a solution architect is a made up role and doesn't do anything and just gets lunch all day and takes a nap.
00:45:00.161 --> 00:45:05.661
You would ask these things and try to connect with the person to say what, what does success look like?
00:45:05.856 --> 00:45:08.675
What is your biggest fear in this role?
00:45:08.976 --> 00:45:13.106
Right, in this position with our teams and then you say, well, how do I disagree with you?
00:45:13.405 --> 00:45:17.485
Productively what manner would be the best for me to bring it up, you know?
00:45:17.905 --> 00:45:18.115
Yeah.
00:45:18.115 --> 00:45:21.746
Again, all three of those underline the need to be vulnerable.
00:45:21.751 --> 00:45:22.226
Right, right.
00:45:22.255 --> 00:45:28.675
And also not have an ego, because if you had an ego, you wouldn't be talking to any of these things so, yeah, absolutely.
00:45:28.675 --> 00:45:32.936
I look how many times have you seen this happen in your professional life?
00:45:32.965 --> 00:45:39.565
Do let us know, but, because I can tell you mine, I can summarize in great detail on the back of a Post-It stamp.
00:45:40.226 --> 00:45:41.755
That's how often I've seen this.
00:45:42.425 --> 00:45:48.576
You know, sometimes the conversation with the architect like it doesn't work because they're holding back.
00:45:48.885 --> 00:46:00.916
There's a difference between an architect who protects the system and an architect who protects the teams that they serve, and an architect who's protecting their own job.
00:46:01.425 --> 00:46:05.496
And let's talk about how to find out which one your architect is.
00:46:05.976 --> 00:46:07.025
All right, let's keep going.
00:46:07.175 --> 00:46:08.286
Oh, the Nygard book?
00:46:08.525 --> 00:46:08.675
Yeah.
00:46:08.675 --> 00:46:09.186
Is that the
one?
00:46:09.221 --> 00:46:09.400
Yeah.
00:46:09.431 --> 00:46:11.210
Oh, do you know this Nygard quote?
00:46:11.210 --> 00:46:11.945
I know the quote.
00:46:12.001 --> 00:46:14.161
I actually own this book from 2017.
00:46:14.221 --> 00:46:15.090
Do you wanna read this quote?
00:46:15.121 --> 00:46:15.420
Sure.
00:46:15.420 --> 00:46:27.005
So this quote again, paraphrasing great architects work themselves out of a job by building the systems and the environment teams, that don't need constant vigilance from them.
00:46:27.306 --> 00:46:27.576
Sorry.
00:46:27.630 --> 00:46:29.311
Work, work themselves out of a job.
00:46:29.340 --> 00:46:30.481
Where have we heard that before?
00:46:32.335 --> 00:46:33.251
that's so strange.
00:46:33.251 --> 00:46:34.990
Someone said, working yourselves outta the job.
00:46:35.110 --> 00:46:35.891
Please continue.
00:46:35.891 --> 00:46:36.460
I'd love to hear more.
00:46:36.760 --> 00:46:37.001
Yeah.
00:46:37.300 --> 00:46:39.490
So that's Nygard's thesis, right?
00:46:39.840 --> 00:46:40.021
Yeah.
00:46:40.021 --> 00:46:43.471
So let's get straight into the, the steel man argument here.
00:46:43.570 --> 00:46:47.891
Architects must stay involved to maintain system integrity.
00:46:48.190 --> 00:46:48.791
That's the first part.
00:46:48.791 --> 00:46:48.820
Yeah.
00:46:48.876 --> 00:46:51.425
So the system doesn't boil over like water in a ca
00:46:51.650 --> 00:46:54.210
means like I have a lot of problems with what you just said.
00:46:54.210 --> 00:46:54.960
Please continue.
00:46:55.650 --> 00:46:57.240
Gimme the second point and then I'll push back.
00:46:57.451 --> 00:46:57.721
Yeah.
00:46:57.721 --> 00:47:01.920
Distributed decision making leads to architectural chaos.
00:47:02.320 --> 00:47:08.615
I was, I don't have, I don't have a beep to bleep out the cursing, so I'm not gonna say anything here right now sorry, was was the second point.
00:47:08.916 --> 00:47:10.056
If we distribute.
00:47:10.431 --> 00:47:13.940
Decision making someone might make a bad decision is that was the second one.
00:47:13.940 --> 00:47:14.090
That's
00:47:14.090 --> 00:47:15.050
exactly what it is.
00:47:15.056 --> 00:47:17.215
and you can't trust them so I'm not gonna let them.
00:47:17.215 --> 00:47:21.056
Oh, so it's this, this is all about maintaining control.
00:47:21.085 --> 00:47:22.916
Exerting and maintaining control.
00:47:22.916 --> 00:47:24.356
Oh man, that's what this is about.
00:47:24.356 --> 00:47:24.985
Sorry y'all.
00:47:24.985 --> 00:47:26.666
I don't think I can, I think I got a headache.
00:47:26.666 --> 00:47:28.436
I gotta Oh no, gotta cut out early.
00:47:28.436 --> 00:47:29.186
You're like that.
00:47:29.306 --> 00:47:33.505
So if those are the best points against like, what a disappointing category.
00:47:33.556 --> 00:47:36.496
What can a solution architect do in this category?
00:47:36.606 --> 00:47:38.496
The best solution architects.
00:47:38.706 --> 00:47:38.976
Okay.
00:47:39.065 --> 00:47:46.251
They help the teams create architectural documents, or at least amend they build on top of wood, supplant them.
00:47:46.255 --> 00:47:46.965
Yeah, absolutely.
00:47:46.965 --> 00:47:47.025
Yeah.
00:47:47.025 --> 00:47:53.606
And they, and they help the teams connect to, to potentially artifacts that they don't even know exist because that could happen.
00:47:53.606 --> 00:48:10.096
It's like, oh, we didn't even know you were using Redis when we came up with this, like queuing home, brewed queuing function each successful solution architect helps the teams make better decisions and go through the approval process in the organization.
00:48:10.215 --> 00:48:13.445
They help them through the approval process.
00:48:13.545 --> 00:48:21.806
I was at an organization one time that was very like the way we think of project management, in terms like you had to go in front of a board.
00:48:21.956 --> 00:48:33.005
They had to review your changes your tests in UAT the results of your feedback to decide if you, and this is software development, by the way, the solution architect really could become your advocate.
00:48:33.166 --> 00:48:37.126
They are like a lawyer at trial counseling you.
00:48:37.126 --> 00:48:42.416
If you decide to be your own lawyer, they're helping you do the best job you can right.
00:48:42.565 --> 00:49:07.956
Arguably they, they could be doing it on your behalf to the group, but most organizations don't work that way but the point is that like they are expertise, again, going back to arguing Agile 67, 6 7 team topologies They're a member of the enabling team loaned to your team for a period of time till you clear a certain decision or hurdle or something blocker yeah,
00:49:08.175 --> 00:49:10.545
they're really catalyzing the discussions.
00:49:10.626 --> 00:49:10.846
Yes.
00:49:10.851 --> 00:49:11.780
Yeah, absolutely.
00:49:11.871 --> 00:49:11.990
Yeah.
00:49:11.990 --> 00:49:20.240
And their value can be measured by how many outcomes they help you get through speed of decision making is one thing.
00:49:20.240 --> 00:49:20.541
The speed.
00:49:20.541 --> 00:49:22.130
Yeah, absolutely.
00:49:22.280 --> 00:49:24.471
But I feel like the opposite is.
00:49:24.891 --> 00:49:30.740
Probably true for most people is that their delay of decision making is how they make an impact.
00:49:30.740 --> 00:49:40.271
Negatively on your team and then the larger organization, it's just that those metrics are not tracked it's harder to hold these folks accountable.
00:49:40.320 --> 00:49:40.501
Yeah.
00:49:40.590 --> 00:49:46.161
They tend to kind of install themselves in these organizations and create these indispensability.
00:49:46.251 --> 00:49:46.610
Right.
00:49:46.791 --> 00:49:48.170
You can't do away with them.
00:49:48.320 --> 00:49:58.641
You have to have approval probably times two or three from these different layers of the, the Solution Architects that you have place with different titles perhaps, but Yeah, absolutely.
00:49:58.940 --> 00:50:03.501
So what we're saying on this specific topic is helping architects.
00:50:04.085 --> 00:50:14.005
Create useful art artifacts, documentation to help the team hoarding architects, on the other hand, they create bottlenecks and dependencies on themselves.
00:50:14.155 --> 00:50:15.146
That's absolutely true.
00:50:15.190 --> 00:50:15.481
Yeah.
00:50:15.925 --> 00:50:16.195
Yeah.
00:50:16.295 --> 00:50:28.295
Your architect who they, they can't take two weeks vacation without everything falling apart or grinding to a halt they're the bottleneck that gold rat warned everyone about ooh, years ago, I mean, decades ago,
00:50:28.876 --> 00:50:29.295
Eli Goldratt.
00:50:29.436 --> 00:50:33.755
You've made yourself into a single point of failure, why did you do that?
00:50:34.115 --> 00:50:35.346
Why would you do that?
00:50:35.496 --> 00:50:36.905
I mean, ego is one side of it.
00:50:37.235 --> 00:50:42.925
I think the complete swing and the opposite direction side of it is ignorance.
00:50:43.226 --> 00:50:43.405
Yeah.
00:50:43.465 --> 00:50:50.126
The ignorance side of it is, is not just simply a passive thing where teams will say, this is above my pay grade, right.
00:50:50.126 --> 00:50:50.905
Or our pay grade.
00:50:51.115 --> 00:50:52.675
This is for the EA to decide.
00:50:53.065 --> 00:51:02.056
This is the other way to so the, these SAs, EAs basically feigning complexity saying, this is too complex for you.
00:51:02.106 --> 00:51:03.905
I'm better position to do this, right?
00:51:04.206 --> 00:51:04.385
Yeah.
00:51:04.416 --> 00:51:06.726
By the way, I'm out for two weeks, so this can wait.
00:51:06.755 --> 00:51:09.295
Okay that, that is very true.
00:51:09.505 --> 00:51:11.215
I've seen that way more often.
00:51:11.215 --> 00:51:20.186
The teams will just be like really struggling to move along without this kind of approval and it's not a tacit approval, it's an absolute approval.
00:51:20.335 --> 00:51:31.815
Like you can't move forward until you get my approval in writing and they have built processes and workflows in place to kind of stem the flow of ideas and forward progress.
00:51:32.175 --> 00:51:38.246
Because these SAs say they are the ones that are the most important cog in the machine.
00:51:38.695 --> 00:51:42.925
Well, let's step back for a minute and talk about what are some things you can put into place.
00:51:43.226 --> 00:51:47.516
To know this is a problem to clearly identify or maybe get over the problem.
00:51:47.706 --> 00:51:51.425
there are four takeaways I got listed here on the screen, which is number one.
00:51:51.456 --> 00:51:53.346
You can give them the documentation test.
00:51:53.766 --> 00:51:55.565
Ooh, what was this documentation test, Brian.
00:51:55.775 --> 00:51:56.826
Hey, calm down.
00:51:56.826 --> 00:52:00.306
Can a new engineer can, can you onboard a new engineer?
00:52:00.576 --> 00:52:04.115
I mean, or really product manager, especially if they're a technical product manager.
00:52:04.686 --> 00:52:05.465
And have them.
00:52:05.840 --> 00:52:14.601
Understand your system architecture without having to have a deep one-on-one with your architect, your system architect off to the side to hold their hand
00:52:14.751 --> 00:52:15.170
who knows.
00:52:15.291 --> 00:52:15.981
Yeah, you're right.
00:52:15.981 --> 00:52:16.431
You're right.
00:52:16.431 --> 00:52:17.751
The documentation test is real.
00:52:17.751 --> 00:52:23.271
So if you can get an engineer to understand things that are documented first, second time, that's great.
00:52:23.360 --> 00:52:23.751
Right?
00:52:23.931 --> 00:52:25.101
Product managers, yes.
00:52:25.161 --> 00:52:27.650
You who really I think is also critical.
00:52:27.655 --> 00:52:33.440
Here are incoming bas do they understand not just the technical diagrams.
00:52:33.445 --> 00:52:33.565
Good point.
00:52:33.565 --> 00:52:33.650
Good point.
00:52:33.650 --> 00:52:40.760
But the business logic workflow, I mean, you're not gonna get everything from a diagram, but you're gonna get the gist of it, right?
00:52:40.820 --> 00:52:40.940
Yeah.
00:52:40.971 --> 00:52:43.431
So there is that test as well, right?
00:52:43.490 --> 00:52:44.541
It's an integral part.
00:52:44.541 --> 00:52:46.311
It's still the documentation test, but do PAs.
00:52:46.610 --> 00:52:48.351
Can they grasp what's going on?
00:52:48.420 --> 00:52:48.990
That's a good point.
00:52:49.240 --> 00:52:52.601
The next one I had was the decision autonomy test.
00:52:52.760 --> 00:52:56.271
The point I had here is you as a product manager, talking to your team.
00:52:56.690 --> 00:53:05.101
What technical decisions can you make without having to involve the architect or the solutions architect or the solutions engineer, whatever, whatever you call 'em, right?
00:53:05.155 --> 00:53:05.545
Yeah.
00:53:05.545 --> 00:53:06.865
This one is a tough one though.
00:53:06.865 --> 00:53:07.585
I'll tell you why.
00:53:07.635 --> 00:53:10.215
So we are talking about senior engineers here, right?
00:53:10.215 --> 00:53:10.726
Not product.
00:53:10.755 --> 00:53:12.315
Oh, you talking, I was gonna say the product people don't have.
00:53:12.960 --> 00:53:18.150
The technical knowhow to understand decisions that pertain to the ities.
00:53:18.201 --> 00:53:25.731
Sometimes when the solution architect decides we're gonna do this, not that they not only need to be able to explain their reasoning.
00:53:26.030 --> 00:53:35.481
Because I, the product manager, as the representative of the business, I have to be able to explain their reasoning to many other people in the organization.
00:53:35.481 --> 00:53:40.130
If it's not clear, if it's like, oh, because I just decided I can't sell that to anyone.
00:53:40.431 --> 00:53:41.451
I can't use that.
00:53:41.541 --> 00:53:43.041
That's not good enough.
00:53:43.150 --> 00:53:48.115
And I only bring that up because a lot of solution architects that I've worked with.
00:53:48.985 -->
00:53:53.025
They go back to that reason and they don't want to expand on any other reasons.
00:53:53.025 --> 00:53:57.106
They just wanna hang their laurels on because I said so, and I'm the architect.
00:53:57.186 --> 00:53:58.746
It's too complex for you to understand.
00:53:59.045 --> 00:53:59.525
Yeah,
00:53:59.641 --> 00:54:02.826
but I mean, look, again, except it's not, but not for you specifically yeah.
00:54:02.856 --> 00:54:14.235
But I'd say product management in general, we're gonna assume even though technical product managers aren't at the same level of technical knowhow, and I know put spa as a, as essays,
00:54:14.286 --> 00:54:16.266
Like even with executives, that doesn't fly.
00:54:16.746 --> 00:54:18.277
They can explain it in terms they
00:54:18.306 --> 00:54:20.280
You gotta speak their language so, yeah,
00:54:20.405 --> 00:54:21.126
I understand.
00:54:21.306 --> 00:54:22.266
But it doesn't happen.
00:54:22.465 --> 00:54:32.661
Okay, so we did a podcast it was arguing Agile 235, changing your message, adaptive versus manipulative communication arguing Agile 2 35.
00:54:32.961 --> 00:54:36.472
This is borderline, but 2 35 is borderline what we're talking about.
00:54:36.472 --> 00:54:37.521
It's not exactly,
00:54:37.672 --> 00:54:38.516
no, it's not what we're talking about,
00:54:38.606 --> 00:54:43.972
I will tell you, I only stopped to search for that podcast because I've.
00:54:44.121 --> 00:54:50.452
worked with many a solution architect who will try to bend the message to fit their narrative.
00:54:50.452 --> 00:54:50.692
Sure.
00:54:50.692 --> 00:54:59.811
Of like, oh, well the product manager was reckless because we said we had this technical dependency or whatever, and he decided to do whatever anyway.
00:54:59.961 --> 00:55:00.202
Yeah.
00:55:00.501 --> 00:55:10.112
Not exactly, because you told me that your connection pooling in the database wasn't that big a deal and it totally should scale to a hundred concurrent users or whatever.
00:55:10.442 --> 00:55:16.672
If the architect is out for a week does our business stop functioning?, I'm aiming this at the solution architect.
00:55:16.972 --> 00:55:19.320
I could aim this at anyone else certainly.
00:55:19.831 --> 00:55:40.646
But I feel these folks that work their way into this position, right, between teams, If they disappear for a week, I think the whole program does grind to a halt and either the program grinds to a halt or a lot of stuff gets escalated over and around the quote normal business process.
00:55:40.675 --> 00:55:40.916
Yeah.
00:55:40.976 --> 00:55:46.115
You like, well, VP Om said we could do it because solution architect Brian is out.
00:55:46.295 --> 00:55:48.905
So he just approved everything while Brian was out.
00:55:48.905 --> 00:55:53.865
If you have organizations where Brian's already put in place all the things we talked about just earlier, right?
00:55:53.865 --> 00:56:00.976
All the documentation, et cetera, and the knowledge sharing, it shouldn't matter That Brian's out for a week or two weeks but yeah, this is what we're saying.
00:56:00.976 --> 00:56:02.416
This is the vacation test.
00:56:02.666 --> 00:56:06.565
I can't think of anything we left outta this category, but if there is, please let us know.
00:56:06.626 --> 00:56:07.255
Yes, please do.
00:56:07.465 --> 00:56:18.085
for the final category on the podcast, we have to talk about when you absolutely must escalate and then how to do it without killing your own career.
00:56:18.286 --> 00:56:19.965
Alright, so let's get to this, right?
00:56:20.016 --> 00:56:25.115
So in the Radical Candor book, kim Scott says, escalation isn't tattling.
00:56:25.505 --> 00:56:30.876
It's caring enough about the outcome to involve people who can change the system.
00:56:31.175 --> 00:56:35.465
That's a wild statement, which leads me to believe we need to do a podcast about that book
00:56:35.615 --> 00:56:37.775
it's a lofty statement to say the least.
00:56:37.775 --> 00:56:38.365
But yeah, good luck
00:56:38.425 --> 00:56:49.090
Listen, if you can change the system and be running up that hill, like that's, I got red texts on a screen most people will say like, Hey escalating a relationship problem.
00:56:49.121 --> 00:56:52.240
I'm like, just doesn't get along with Brian to leadership.
00:56:52.481 --> 00:56:53.621
That's gonna make you look bad.
00:56:53.670 --> 00:56:55.471
it is 99% of the time.
00:56:55.530 --> 00:56:55.710
Yeah.
00:56:55.951 --> 00:57:02.190
Unless HR already has a thick file with two Cs, a thick, a thick file.
00:57:02.490 --> 00:57:03.360
On that other person.
00:57:03.416 --> 00:57:03.715
sorry.
00:57:04.025 --> 00:57:08.786
Like it's gonna make you look bad and there's just no reason to put that on your career.
00:57:08.936 --> 00:57:09.206
Right.
00:57:09.335 --> 00:57:12.635
the other side is like, Hey Om, you're a professional.
00:57:12.905 --> 00:57:20.525
I expect you to resolve whatever it is with the other person without quote, bothering leadership.
00:57:20.876 --> 00:57:21.115
Yeah.
00:57:21.115 --> 00:57:25.811
So escalating with it, it depends on your org structure or your org culture.
00:57:25.931 --> 00:57:31.831
You could do that or if you could do that, but if escalating reasonably frequently doesn't bode well for you.
00:57:32.021 --> 00:57:34.121
You know, HR is going to put you in a bucket.
00:57:34.322 --> 00:57:36.181
It's the right thing to do when.
00:57:36.572 --> 00:57:39.242
You've tried things and you have evidence.
00:57:39.242 --> 00:57:45.800
Don't just go in and without evidence and say here's the problem you tried something and you can absolutely back it up.
00:57:46.070 --> 00:57:46.851
Okay, escalate.
00:57:46.880 --> 00:57:47.510
That's fine.
00:57:47.840 --> 00:57:49.221
But don't do that all the time.
00:57:49.221 --> 00:57:52.456
Also, don't escalate the person escalate the problem.
00:57:52.786 --> 00:57:53.596
Oh, good point,
00:57:53.715 --> 00:57:58.157
How
does your organization perceive and handle such escalations, right?
00:57:58.157 --> 00:57:58.246
Mm-hmm.
00:57:58.487 --> 00:57:59.835
That should be your starting point.
00:57:59.835 --> 00:58:00.045
So,
00:58:00.076 --> 00:58:01.706
So I got the points here.
00:58:01.766 --> 00:58:02.576
They're on the screen here.
00:58:02.695 --> 00:58:02.846
Okay.
00:58:02.936 --> 00:58:16.166
So in order, you said, don't escalate the person, escalate the, the decision making process is broken or the issue that came up because a current process is broken.
00:58:16.166 --> 00:58:17.856
So you're basically escalating.
00:58:18.036 --> 00:58:20.585
We need clarity on how to resolve this.
00:58:21.141 --> 00:58:30.010
Thing that happened, you're not saying, we need you to make a decision that this person's bad, or you need to call out this person as being bad or whatever.
00:58:30.192 --> 00:58:30.402
Right.
00:58:30.492 --> 00:58:32.172
Because that's just not gonna happen.
00:58:32.516 --> 00:58:35.956
And I have to go back early in my career for me doing this kind of stuff.
00:58:36.286 --> 00:58:41.155
'cause earlier in my career my attitude is like, this person sucks, like this super unresponsive.
00:58:41.456 --> 00:58:42.865
Like they're bad at their job.
00:58:43.016 --> 00:58:45.115
I have to kick their back to them two or three times.
00:58:45.425 --> 00:58:47.166
Say tackling the person, not the problem right there.
00:58:47.215 --> 00:58:52.135
It would've been tough advice to give to myself at that point in my career.
00:58:52.596 --> 00:58:53.826
Now, where I'm later in my career.
00:58:54.335 --> 00:59:00.155
I would go over and sit with that person and be like, I'm here to sit with you until we've worked through the issue, you know?
00:59:00.365 --> 00:59:03.485
So that you know that like you need to dedicate your full
00:59:03.635 --> 00:59:03.876
Yeah.
00:59:03.965 --> 00:59:04.746
Brain power to it.
00:59:04.746 --> 00:59:22.577
Or maybe I can help you come off of the decisions that you're on or delays or whatever if you've got a lot of stuff going on, I'll sit with you and work through that with you frame it as we need clarity on how to resolve this situation, not blaming it on the person, again, building on the previous step.
00:59:22.786 --> 00:59:26.137
And then the final point here on the screen is when we disagree.
00:59:26.336 --> 00:59:29.217
. How should we make this decision when we disagree?
00:59:29.697 --> 00:59:32.367
I'll tell you how, how it went for me when this happened.
00:59:32.427 --> 00:59:38.036
Early on, very early in my career, I did escalate and I did tackle the problem, not the person.
00:59:38.117 --> 00:59:40.967
But they said, well, who's normally your go-to?
00:59:41.297 --> 00:59:41.686
Right?
00:59:41.927 --> 00:59:46.606
So at that point, you have to say the name, which I did, and they say, well, they're indispensable.
00:59:46.606 --> 00:59:47.847
Yeah so here's what we're gonna do.
00:59:48.146 --> 00:59:50.967
We're gonna give you somebody else who will help you.
00:59:51.387 --> 00:59:53.786
And that somebody else was this person's peer.
00:59:54.336 --> 00:59:56.436
and they were both from the same nest.
00:59:56.677 --> 00:59:59.766
So this guy made the same decisions as the other person would've made.
00:59:59.766 --> 01:00:08.811
Course it didn't get me any further but it was a lesson learned from me, which is understand your organization and see which way you wanna go after that.
01:00:09.112 --> 01:00:12.931
So again, that of course you learn to course this is one of those I chalked it up to.
01:00:13.242 --> 01:00:14.322
it's an experience thing.
01:00:14.322 --> 01:00:14.922
lesson to learn.
01:00:14.981 --> 01:00:17.442
Alanis Morisette said, taught us you live, you learn.
01:00:17.492 --> 01:00:28.521
To wrap this category, if you're afraid of escalating a broken process, because it might hurt someone's feelings, like at that point you care about being liked or stepping on toes or politics too much.
01:00:28.702 --> 01:00:29.001
Yeah.
01:00:29.052 --> 01:00:31.481
More so than you care about delivering
01:00:31.692 --> 01:00:32.262
value.
01:00:32.561 --> 01:00:33.192
Absolutely.
01:00:33.192 --> 01:00:36.382
Or you just care about preserving your own job.
01:00:36.621 --> 01:00:36.922
Okay.
01:00:37.001 --> 01:00:39.581
I'm going to sail through the takeaways here.
01:00:39.771 --> 01:00:40.791
Document the pattern.
01:00:40.791 --> 01:00:42.052
We already talked about documenting.
01:00:42.331 --> 01:00:54.251
You might want to quantify the impact if nobody else has, more likely they have to say that like, Hey, this, this decision process has delayed X amount of features for y amount of weeks.
01:00:54.746 --> 01:00:58.467
Affecting the amount of customers pot, even if it's all potential.
01:00:58.737 --> 01:01:00.237
At least you're putting some numbers behind that.
01:01:00.237 --> 01:01:00.297
Yeah.
01:01:00.327 --> 01:01:01.677
You're dealing with the problem.
01:01:01.677 --> 01:01:03.447
You're not blaming a person at this point.
01:01:03.496 --> 01:01:09.286
You're just saying, Hey, because we had to delay these decisions because of this organizational process.
01:01:09.286 --> 01:01:10.246
That's what we're saying.
01:01:10.547 --> 01:01:19.657
I know it might come across, especially when ego gets involved, it might come across as, oh, this one person hasn't made the decision or went on vacation, or whatever it is.
01:01:19.657 --> 01:01:21.621
Yeah Hey, hey, hey, I'm not talking about that person.
01:01:22.192 --> 01:01:25.791
I'm talking about the organizational process that we're following now.
01:01:25.972 --> 01:01:26.871
That's what I'm talking about.
01:01:27.141 --> 01:01:27.322
Yeah.
01:01:27.322 --> 01:01:32.442
Just aim for a one pager that just says The cost of delayed decisions or decisions not made.
01:01:32.742 --> 01:01:42.092
And then proposing a fix is as easy as what I outlined, when I said you just ask for the decision making process.
01:01:42.092 --> 01:01:45.061
When it's unclear, you ask for that to be clarified.
01:01:45.271 --> 01:01:45.452
Yep.
01:01:45.797 --> 01:01:46.067
Yeah.
01:01:46.556 --> 01:01:49.757
document the pattern you need the more examples, the better.
01:01:49.817 --> 01:01:51.827
Three examples is pretty good.
01:01:51.827 --> 01:01:54.806
You quantify the customer impact, you propose a fix, you know?
01:01:54.947 --> 01:01:58.697
'cause there's a lot of psychopaths out there that say, Hey, don't bring me problems.
01:01:58.697 --> 01:01:59.601
Only bring me solutions.
01:01:59.601 --> 01:02:02.831
Only bring me solutions because I can't be bothered to think That's right.
01:02:02.942 --> 01:02:03.512
Exactly.
01:02:03.572 --> 01:02:06.422
Alright, so this one, what do you think about this category?
01:02:06.472 --> 01:02:07.911
What do you think about our solutions?
01:02:07.911 --> 01:02:10.672
Here are three very simple questions here.
01:02:10.981 --> 01:02:11.972
Let us know in the comments.
01:02:12.032 --> 01:02:12.302
Yeah.
01:02:12.302 --> 01:02:16.981
And if you're an S.A., please give us some thoughts that you have around this podcast too.
01:02:17.612 --> 01:02:20.471
But also don't forget and subscribe.