337 - User Testing, Paper Prototypes, and Escaping Hourly Billing with John Athayde
1 hr 18 minAudio
In this episode I talk with John Athayde, designer-developer and co-author of The Rails View, about what architecture school taught him about software design. John tells the story of a user test at LivingSocial that exposed a confusing scheduler, and explains why testing with as few as five users finds most problems. He also explains how he paper-prototypes by acting as "the web server." We discuss why AI-generated interfaces often look polished but are built on meaningless markup, why copy should come first, and how to move from hourly implementation work to higher-value advisory consulting. Links: - Meticulous - Sfumato Farm - John Athayde on GitHub - Standard Agents - Hourly Billing Is Nuts (Jonathan Stark) - Why You Only Need to Test with 5 Users - Nonsense Monthly
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
SPEAKER_02Hey, it's Jason, host of the Code with Jason podcast. You're a developer. You like to listen to podcasts. You're listening to one right now. Maybe you like to read blogs and subscribe to email newsletters and stuff like that. Keep in touch. Email newsletters are a really nice way to keep on top of what's going on in the programming world. Except they're actually not. I don't know about you, but the last thing that I want to do after a long day of staring at the screen is sit there and stare at the screen some more.
SPEAKER_02That's why I started a different kind of newsletter. It's a snail mail programming newsletter. That's right. I send an actual envelope in the mail containing a paper newsletter that you can hold in your hands. You can read it on your living room couch, at your kitchen table, in your bed, or in someone else's bed. And when they say, What are you doing in my bed? You can say, I'm reading Jason's newsletter. What does it look like?
SPEAKER_02You might wonder what you might find in this snail mail programming newsletter. You can read about all kinds of programming topics like object-oriented programming, testing, DevOps, AI. Most of it's pretty technology agnostic. You can also read about other non-programming topics like philosophy, evolutionary theory, business, marketing, economics, psychology, music, cooking, history, geology, language, culture, robotics, and farming.
SPEAKER_02The name of the newsletter is Nonsense Monthly. Here's what some of my readers are saying about it. Helmut Kobler from Los Angeles says, thanks much for sending the newsletter. I got it about a week ago and read it on my sofa. It was a totally different experience than reading it on my computer or iPad. It felt more relaxed, more meaningful, something special and out of the ordinary.
SPEAKER_02I'm sure that's what you were going for. So just wanted to let you know that you succeeded. Looking forward to more.
SPEAKER_02Thank you for this. Can't wait for the next one. Dear listener, if you would like to get letters in the mail from yours truly every month, you can go sign up at nonsensemonthly.com. That's nonsensemonthly.com. I'll say it one more time. Nonsensemonthly.com. And now without further ado, here is today's episode.
SPEAKER_02Hey, today I'm here with Jonatha. John, welcome. Welcome. Thanks. How's it going? Doing good. This is your second time on the show. I just checked. You were on episode 89.
SPEAKER_00It's been a little while though.
SPEAKER_02Yeah, yeah. As of this moment, I have like 325 episodes published. So it was a couple hundred episodes ago. What are you up to these days? And also, if anybody didn't catch that first episode with you, um, tell us a little bit about yourself and what you do and that kind of stuff.
SPEAKER_00I am a uh a borderline unicorn. I think we'll start with that. That's always the fun way to put it. Uh I'm a designer that went to architecture school and taught myself print and then taught myself coding at the same time. Started off in in Apple HyperCard, if you can go back that far on a little black Mac and white, uh black and white Mac SE, and um just kind of grew into PHP and all those things. And so I've always been kind of just growing up with the web, and there was never this you have to choose a path, you just did all the things. Uh, and I never caught the memo that I should specialize.
SPEAKER_00So um that's basically my high-level um kind of thing that I'm you know, broad-based designer developer, been working in Rails since uh we shipped our first CMS in Rails right as 1.0 was going live. Um, and I've jumped between, you know, doing uh employment, like I was at Living Social with a really great team of uh Rubyists and um and then doing things like uh you know startups like Cargo Sense and Occupy and things like that, and uh been back on my own now doing consulting for Meticulous, which is my company that it's been around since 97.
SPEAKER_02Okay. Um yeah, I I don't consider myself any kind of borderline unicorn or anything like that, but I do fancy myself somewhat of a designer or a programmer who does design and I educate myself on design and stuff like that. Uh I think I knew that you went to school for architecture. Um and I think it's interesting because there's like universal design principles that apply to everything.
SPEAKER_02For sure. Um maybe we can talk about that for a second. I'm sure there are things that have carried over from that to this. Is that the case?
SPEAKER_00Yeah, and I think it it's it's um there's a couple running jokes from architecture school that that I think apply. Um one is that an architect learns uh less and less about more and more till they know nothing about everything. And when you have an engineer, that's the inverse, right? They're a hyper specialist typically, right? You're a civil engineer, you're an electrical engineer. Um that's that's kind of uh very stereotypical, and it kind of makes both sides look kind of bad. But the the architect is very much the generalist, they have to be able to understand, translate client problems into design solutions.
SPEAKER_00And those design solutions in that case take effect in the physical world. They are they are physical changes that we are going to make to the environment. Uh, that could be in landscape, that could be in physical structure, uh, all sorts of different things. Um, and their their goal is to improve the outcome for that person um and or or people. Uh uh, then you also have sorry, I've got the cat walking all over the desk today. Then we've got uh things like where you you start looking more at um the the way that the architect works.
SPEAKER_00And I've always thought that designers kind of at least on the website lost this thread early on, unfortunately. If you look at how an architect runs a project, the architect is the client's representative to everybody. So if you hired me as an architect, I am going to be my my goal is to make sure that your what you want is built. And so there is the drawings themselves are a legal contract. They are part of a legal contract that's admissible in court, and therefore everybody who's doing those pieces of work has to design to that spec.
SPEAKER_00Now, there are a series of things like change orders and submittals and things like that where they say, Hey, I'd like to make this modification, can you please approve it? Um, and it was kind of fun because this is actually the software that I helped design the early days of it, Procore, was very much turning that world into software. And so it was really cool to get to use my degree and design in a Ruby shop. It was like you know, holy grail. Um, but but that's the kind of stuff like the designers in in our our part of the world with software don't have that kind of carte blanche.
SPEAKER_00Maybe product managers do, um, but it's it's kind of been removed in in a weird way. So I feel that we we've lost that thread, unfortunately, on on the design side, but it is about solving design problems. So there's a lot of UX people actually that went to architecture school that I know, and it's it's really interesting to kind of see how we all approach it from the same kind of high-level thing. We're thinking about things very there's a lot of systems thinking that happens in architecture training. Um, there's a lot of um what would be more um I don't have to build the wall, but I have to know how the wall is built.
SPEAKER_00So a lot of us have dabbled in all sorts of different pieces of technology to understand. Oh, how you know, if you don't understand how a request happens, how can you design to a request? Things of that you know, at a very basic level, but you can get into way more complex things there. So most designers have had to pick that kind of stuff up, but I feel the ones that went to architecture school just kind of started there. We just immediately were like, I need to know about that because I gotta design that. I can't design it because I don't know about it. So let's go figure it out. Um, and maybe that's uh maybe that's me defending my path.
SPEAKER_00But but I feel like a lot of the people I've talked to that that came on a similar one dabble in in similar ways, and they have a different they have a similar kind of uh camera shift, right? Uh of how they're looking at everything. So it really is kind of the the liberal studies of design in a weird way. It's it's um some of the some of the people I went to school with went into fashion, for example, like right, they went into fashion design, things like that. So it's very it is very broad based, and you can apply the design principles, figure ground, and all that kind of stuff you learn as the basics. Uh it's it's different though than print.
SPEAKER_00Like the stuff you learn in prints in in graphic design school is far more uh it's it's like a narrower communication thing. We have a part of that in architecture, but I think again that's where you start becoming a little more specialized. And and granted, there are print designers that that knock my socks off and I things I could never do. I'm just they're way better, and that's totally cool. Um, but it's yeah, I've got that very very broad line with a couple descenders or however you want to talk about that multiple T individual.
SPEAKER_02Yeah, um one of the more tragic mindsets that is prevalent in programming is like, okay, I made this feature work. Now I need a designer to make it pretty. And it's like, no, no, no, no, no, no. Um there's that famous Steve Job quote, Steve Jobs quote, uh design isn't just how it looks, it's how it works, or whatever it exactly it was. Um and I'm really glad that you touched on the fact that that uh design is largely about uh design solutions to design problems.
SPEAKER_02It's not just about aesthetics. Like aesthetics is definitely part of it. Sure. Um but but it's about solutions to problems. Um and like if you start with a feature and then you're like, all right, let's let's add some design to this feature that's like totally it's not even wrong. It's like it's so wrong that it's it can't you can't even call it wrong.
SPEAKER_00Right. Yeah. Correct. Yeah, and I think if you I I've said this a lot 'cause because you I've had engineers say, Well, I can't design. It's like every decision you make in the code base is actually a design decision if you think about it that way, and I think you should think about it that way. Because invariably, if we say, Oh, design is just the pretty, well, we've we've created a weird silo that shouldn't exist. And we've relegated that to visual design only, which is a very small subset of of how things should be.
SPEAKER_00Um and I think service design as as a kind of a practice on our side of the fence is the closest thing we've got to architecture. Because you start talking about the entire life cycle of a person with the organization, right? So you're not just saying, Oh, I need engineering and I need product, I need marketing, I need support, I need I need finance, I need the entire company. We're designing the company, we're designing the product and how the company interacts and how people interact with our product in the arc of their life, in the arc of their day. You know, these we don't just sit there and surf, well, we shouldn't just sit there and surf Facebook all day.
SPEAKER_00Some people might, but in you know, in general, usually there's a notification, it's something, oh, I want to reply and say congratulations or whatever to somebody, you know, and I'm sure younger people are like, You use Facebook, dude, what up? But or something like that, right? But uh, but but any of those kind of tools, any kind of kind of social media or any kind of platform, it's usually being it's coming and going. Things are things are are transient. We're not saying, oh, I'm I'm sitting at this screen and I'm I'm not distracted and nothing else happens. And I think one of the big failures we have is that because of budget cuts in general, testing was one of the first things that kind of got user testing, because it's expensive and it's difficult, right?
SPEAKER_00I need to get people together, I need to have them do things, I need to, it's a lot of subjectivity, so I need to analyze a lot more compared to say, did you know, when I'm writing an automated test, did the button click? I can just have Bin CI run, I can go work on something else while that's cranking through it. It's part of our pipeline to publish, right? That's that's a different kind of accepted thing. And that catches failures, but that doesn't catch, oh, this is weird, because I've I'm holding a child at a bus stop trying to work with my non-dominant hand on a phone in bright light.
SPEAKER_00Now, now we've changed a whole lot of the operating environment, right? So, what starts to change with how I interact with that? Um, and those are the kind of things that are are difficult. And and I think that's where that's where you start to see like some of the people that have really spent a lot of time and been able to push products really far, that's where they start to get to. And I think a lot of the complaints we see about like the current Apple stuff is we they used to do that kind of stuff for sure. And it feels like they're skipping some of that. I don't know if they are or not, but some of the UI stuff that's shipping, we're like, you didn't test it?
SPEAKER_02Yeah, it's it's truly tragic what has happened to Apple. Um I I want to dig deeper into testing, um, because maybe not everybody is familiar with what that means exactly. Um, the way I think about this is like, how do you know if a design is any good? I I I think most people's conception of that is like, well, you have a designer do the design and you just kind of trust them, and if it looks good, then it's good.
SPEAKER_02But that's that's really not it. So can you tell us about what user testing is and what purpose it serves?
SPEAKER_00Yeah, so I think um I think if you go back to more user experience, right? We that we need to incorporate some of these things that have been peeled off through a variety of different decisions. If you have sorry, I think you're hearing the cat or the rooster, I'm not sure.
SPEAKER_02Yeah, I'm like I hear some kind of voice in the background from some human or non-human animal.
SPEAKER_00We've got we've got new chicks over. I mean, this is my I'm in my barn office for people that are just listening, right? So over there is is you know, there's there's four four hand four birds that we we got from school that are growing up and they're about to start turning into roosters, so that sounds like an early rooster call. Um I'm in my barn office also.
SPEAKER_02What awesome. You know, how often do you have two people on a podcast, programming podcast nonetheless, who are who are both on their barn office anyway.
SPEAKER_00This is the this is where we just gotta be like, come on, we gotta have like a little, we have to have a breakout session at Rails World or something like that, where we are at Ruby conference next time. We get to have like you know, coders who farm or farmers who code or whatever. Exactly. All right, sorry, we can reset on that one. Um so testing, user testing. If I'm looking at um it's more we gotta go back out and and and expand out beyond like contrast. So we've got the basic accessibility stuff is just like that's table stakes, and that's stuff we can automate, right?
SPEAKER_00So is our is my contrast ratio okay on these buttons? Is you know things of that nature? Is is do we in in the code, are we doing the proper kind of navigation landmarks? Are we using the semantic markup? Are we doing all these things that are the bare bones WCAG 2.whatever double A, right? Like that's that should be a gold standard just to for to put something into market. It's not, but that's kind of where I would encourage any company just to just start with that. Because it's one, it's automatable by and large. Um, if you're thinking then about now interaction with that product, that's where things start to get complex.
SPEAKER_00So this is where things often break down very quickly. It makes sense because I can check the boxes and say this is the happy path. But now, what is every potential break on that happy path? And I want to try and trigger that, and I want to see how someone recovers from that. And there's a variety of of things that have been established over many years um that are kind of called heuristics, and this is an easy place to start. So you can look up like the 10 heuristics, but it's it's um there you can deep dive in every single one of them. There's a lot of information out there, but some of them are things such as um state of the system, is is this working or not?
SPEAKER_00Is is this something I can do? What am I in an edit mode or not? Like, is are these things clear to an end user? And if so, then how do we represent those visually and make sure that they're they're easy to understand? Um, you know, if um you can start talking about also the efficacy of a system, like how easy it is for someone to understand what they're looking at, and then how quickly they can accomplish a task that they need to do. So, one thing we often measure when we're doing a redesign is is time on task. So it currently takes support uh four minutes and seven seconds to close a call or to to to close a chat.
SPEAKER_00And we would like to improve that by 10%. Can we do that? And that's kind of a the the metric, and that's one of the things like at Living Social, that's one of the things we did do. Like we had very clear timelines and people dropped like drop calls, like people would be on hold for so long that they got perturbed and dropped the call, like on a support call, which is a horrible place to to to end up. Um so getting that done would is was something that you know we could we could actually say, hey, we reduced call drop from from from whatever 70% to 20% or something like that.
SPEAKER_00I don't remember the number, it's been a decade now. Um, but that's the kind of stuff that you can look at and be like, oh, really cool, great, we've we've solved that.
SPEAKER_02Um I'm sorry, one second. Oh yeah, go ahead. Uh while you're doing that, I'm gonna make a comment. Um so I might make a uh a food analogy here. Um actually I'm gonna I'm gonna wait.
SPEAKER_00All right, sorry about that. I've got turkeys I had put in the bag and forgot to take them out.
SPEAKER_02Oh, no problem. Uh I'll cut that part out. Um so I might make a uh an analogy here. Um about just like testing any kind of product. Um the first thing that comes to mind for me is food. There's that uh expression, the proof of the pudding is in the eating. Um I learned by the way that the word proof means test. So the the test of the pudding is in the eating.
SPEAKER_02Um like a scientific proof. Yes. This pudding is scientifically tasty. Um you can test food yourself. You can make some food and then eat it and decide whether you think it's good or not. Um, and that's a valid test, but it's not exactly the same thing as like if you open up a restaurant in a neighborhood that you don't live in and the demographic is different people from you. It's like, okay, I like hot dogs, but do these people like hot dogs?
SPEAKER_02Is this rest for from a business perspective? Is this good food? Um, and it may be that that's the wrong demographic for that food or whatever, and so even though you like the food, it doesn't mean it's it's viable from a business perspective. Um and so you have to test it. You you have to give some some of that food to the people who are actually gonna eat it, or like people who are representative of those people who are gonna eat it and see if they like it.
SPEAKER_02And that's not even that's not a very good example because that's that's like relying on what people tell you. Like, hey, do you like this food? Oh yeah, it's good. Uh can you change?
SPEAKER_00No, it's great, nothing. And they they don't wanna they don't want to hurt your feelings, so they don't tell you the answer, right?
SPEAKER_02Yeah, exactly. And that's actually like the worst example I could have picked because that's that's what a lot of people think. Like, what do you think of this feature? Oh yeah, it's really easy to use. But then the second you leave them alone with it, they get confused and and they can't use it. Um you have to test it empirically. Um what's what's a product that you might test uh that you might test empirically?
SPEAKER_00So we did this was um we had a scheduler we built At Living Social. And this was something the great thing about working there is we were doing internal tools on my team. And so I had really amazing access to my end users, which is not always the case, right? But when you do have it, abuse it, right? So um we uh Brenda Campbell was doing, she was the product lead on this. We were doing a scheduler, and we used a tool that's not out anymore, it's called Silverback. But the concept was that um you can do this with other tools now. It recorded the screen, it recorded the person via the screen camera, and it recorded their clicks so you could see what they were doing.
SPEAKER_00And the great thing about this was instead of having 20 people hovering over this person's shoulder, you just had to sit down with the product person or or anybody who was going to run this test. Everything had to be, and what would you know, talk me through what you're doing? Okay, you know, that the ta what we'd like you to do is try to schedule something. Make it very much like what are the daily tasks that they're doing, and now talk me through what you're looking at, what you're trying to do, what what things are weird, things that you don't understand, things you do understand, uh, and and let them narrate their their drive. That was really compelling, and it's funny because I didn't realize how much people would just randomly click on a screen, and I'm sitting there and the screens like you look at the video, I still have it somewhere, and the screen's like lighting up with like just these green, like every time it clicks, it's like a radar ping on the screen, and I'm like, oh my gosh.
SPEAKER_00And um, we realized very quickly that you know they they didn't realize it was a drag and drop interface because we hadn't told them, and it was a brand new interface. So that was very important because they were clicking and oh, I moved something, wait, what? You know, and so some of that's discoverable, and it was like, oh, they could fix it, but maybe you should start with a little more, a little more tour or something, right? Maybe we need a little more of an onboarding here of what happens just to say, hey, you know, here's here's kind of a you know a five-minute tour that you can skip, right? Or something like that, just to bring somebody on onto the platform faster. Because there's a balance between making something super simple to use and then crippling power users versus having power user tools that are impossible.
SPEAKER_00Like you open Photoshop for the first time, you've never done it, you have no idea what you're looking at. It's gotten much better because it used to just be an empty screen. Now they kind of have a would you like a tutorial or here's your recent files. You know, so they've they've kind of started working towards that as well. But um it's it's difficult to say, you know, that that balance is always a fine line, and you have to kind of figure it out. And some some tools we've even seen too, where they've got like an easy mode to start, and then you can like start turning all the things on, especially when you look at like bigger platforms like CAD systems, like VectorWorks is a good example, right? They've got a uh you know a basic level where they have only the really the key tools you need to do some of the basic work.
SPEAKER_00Then you can go into architecture or the the um landscape module or the the entertainment module, like stuff that you knew you need to know a lot more about what you're doing, and it's gonna take training to get there, but that's okay because at that point you're also you know invested in a you know$800 a year seat or something like that, right? So you're you're not just gonna buy that for for willy-nilly. You've you've already said, yeah, this is the tool I want to use, and and I'm invested in learning it. But um, yeah, a lot of that stuff is just figuring out the the the way to ask the question without leading the person and and getting them to talk through it.
SPEAKER_00It's really hard to to to get that narration happening, but once they start talking about it and it's like, oh, there are no wrong answers here, I'm just gonna tell you what I'm seeing, then you get some really great stuff. And the great thing is if you record that, you can go watch it again. So you don't have to be scribbling notes, you're just having a nice conversation about a product with somebody. And they're not like, what are you writing down? What's going on? Right. Um, so that that tools like that are really powerful in being able to run those tests. And again, it's gonna be a subset, right? The more you uh there's a you can, you know, there's diminishing returns, but um there's also like too little.
SPEAKER_00So if you only do one person, probably a bad idea. If you do if you schedule 400 people, well, I'd like your budget. And um, and I don't think most people just, you know, that's that's a kind of testing where it's like, wow, I mean, maybe somebody like a large Google or somebody like that's gonna do that kind of level of testing. Um, but usually you're gonna find a lot of issues in five to ten people. There's a you know, Nielsen has some tests where he shows a graph and it's only five, and I think that might be a little low. I think it really depends on the complexity of the product and the complexity of the user base, right?
SPEAKER_02Uh if I may interject, yeah. Um, in my experience, for the early rounds, it just takes one person.
SPEAKER_00Well, yeah, just one will get you like on on initial product stuff, yeah, and you you you'll see all sorts of issues really fast.
SPEAKER_02Yeah, because usually my first swing at the design is so bad uh that the first person uses it and it's just not even usable remotely. And so I'm like, okay, I need to like make some drastic adjustments, and then I give it back to that same person and it it goes better. And then I can go to more and more people and get finer and finer feedback. But in the beginning I find that j just one is all I need.
SPEAKER_00Yeah, and you can even do it really informally. You can do this is something I've talked about with like the Starbucks test, right? If you're just sitting there, hey, could you take a look at this? I'll buy you a coffee if you'll tell me what you think about this for 10 minutes. Uh, you know, some some people be like, go away. But I mean, also it's somebody that has zero baseline, right? They've never seen this before, which is really the hardest thing when you're testing. If you keep showing the same thing to somebody, now they've got a history with the product, which is good and bad. Like, you don't I mean that that it's just different, right? You need to think about okay, from of going from zero versus going from tried it already.
SPEAKER_00What what do I get? What do I see? Because somebody's got a preconceived notion of this, or they're coming in saying, like it used to be, it used to be an issue where you'd say, Well, people don't know software, right? This was really an issue more before the iPhone came out. And it was like, oh, corporate software is just this special thing, and then you have home software and it's a different thing, and and people don't really get between those things. But now everyone has an expectation of software based off of having used mobile apps. So if you if you're not being aware of that as you're building your product and testing your product, you're gonna have people say, Well, this doesn't make sense because their mental model is Facebook, Instagram, TikTok, whatever, or you know, just or mail or safari or Chrome, whatever they're used to using.
SPEAKER_00So that's very that's always something important to say with like what is the baseline somebody's coming in on, because that's gonna affect what you want to ask, how you want to ask it, and how you want to, you know, you don't want to steer too much. You really do want to get as raw feedback as possible. But if somebody's going off a rabbit hole, then you're like, you know, the question is, is this valid? Did I totally miss the mark? Sometimes the answer is yes, and it's like ah crap. Okay, going back to square one. But um, sometimes they're they're just hung up on something. And you'll see this too. We have this issue with when we're doing like brand or design pitches, and somebody's like, Well, I don't like that green.
SPEAKER_00One of the reasons we always do first pass on logo marks is always just black. It's just a black, it's all it's 100% black on white. There's no color involved, is because we're talking about the shape. And once people start looking at the color, we're like, I don't like that green. So they reject an idea not because of the shape, but because of the color. Well, the color is easy to change, but for somebody who's not in that creative mentality or not thinking about that, they they can't maybe can't get past that. That color is currently green. So this is the same kind of thing where you gotta, what are the preconceived ideas? How do I minimize those?
SPEAKER_00And it's, you know, again, we're trying to run some scientific experiments as much as we can. How do I get clear outcomes and clear clear uh answers on this test on and on the um the user's perception of the product in its current state?
SPEAKER_02Yeah. Um and it's it's here's here's how I have usually done those tests when I've done them. Um like I certainly don't ask the person like, what do you think of this design? Um I give them a list of tasks to carry out. Like, for example, if it's a scheduling system, I say uh John Smith calls and he wants to make an appointment for Tuesday at 9 a.m.
SPEAKER_02Yep. It's 45 minutes long, schedule that appointment in this system. Yeah. And I tell the person, like, I'm not gonna give you any hints, I'm just gonna sit here and observe. I'd like you to talk out loud as you try to carry out this task. And if they can't figure out how to do it, it's very tempting to give the person hints, but that's that's not the right move. Uh, because if you give them hints, then you deprive yourself of the feedback and learning.
SPEAKER_02Right. Um and if if they get confused, it's probably not their fault, it's probably the fault of the design. It's easy to make the mistake of thinking that the person is just dumb. Um, but then it's like, oh, this person's an idiot, they can't figure out how to do this. But then you you show it to the next person and they can't figure it out either. And then the next person, the next person, the next person, they all fail on the same spot, and it's like, oh wait, maybe they're not the dumb ones, maybe it's my design that is dumb.
SPEAKER_02Yeah, which can be hard to admit sometimes.
SPEAKER_00But it is, and and you hope that the people don't go into the Homer Simpson, this is everybody's fault but mine response. But sometimes they do. Uh, and as a designer, you have to be like, guys, no, we we missed, we missed, we got to try this again.
SPEAKER_02Mm-hmm. Yeah, um, and I don't want anybody listening to get the idea that they need to learn a lot of stuff before they start doing this. Um, because at the essence, you're just seeking some empirical feedback on your design. Um, and for my first rounds of design, I would even just do pen and paper. Like for the scheduler system, I might um draw on a blank sheet of printer paper um the uh the form to schedule a new appointment with the date time field, uh client name, whatever.
SPEAKER_02And then I just have the other person, assuming this is an in-person exercise, I give the other person a pen and I say, here, I'm gonna act as the web server and slide pieces of paper across the table to you, and then you're gonna use the pen to fill out the fields and to click on things by touching the pen to the paper. And again, I act as the computer, and so they fill something out, submit it to me, and then I give them the subsequent page.
SPEAKER_02It's it's a very lo-fi exercise. It takes pretty much no expertise, takes no special software or equipment or anything like that. Um, so it can be done in a very lightweight way with not a lot of uh special knowledge or skills or anything like that.
SPEAKER_00For sure. And paper prototyping is is one of those great toolkits that um I think everybody should use. I still going back to the architecture thing, I still draw a lot of my site designs on 12-inch architectural trace because you can overlay it and and do you know quick copies of of repeating elements and stuff. But that's just that's just force of habit for you know coming out of school. I just kept using it and I always have. And um it's funny, there's um it's faster for me. Like I kind of dread Figma. Uh I mean it's a very powerful tool, but like I know I've it's more of an archival process, it's less raw, it's less, it's it's less design.
SPEAKER_00And uh there's a quote one of my friends from school, uh Adam Hermanson, uh posted recently that he reminded me from one of our profs who used to say, an architect thinks with this pencil, and uh and that it's just one of those things that's been just you know scratching in in my brain for a long time. And it's it's the nature of writing. And this is this is just not just drawing design, but the nature of writing is different than typing. It changes a different brain pattern, and so you're actually doing different things, and so there's there's something to be said about drawing the interface or drawing out the even the flow or anything like that versus putting it in uh an archival process and making an artifact in Figma or some other similar tool that I think is is lost sometimes.
SPEAKER_00And this could be a whiteboard, it doesn't have to be paper, right? I mean the any any variety of of elements like that. And the the benefit is is anybody can participate in that. It doesn't feel like I have to be a great artist because let's be honest, it's really hard to write write clearly on a whiteboard to begin with, and so you just kind of hand the pen over to somebody and they get up and they start scribbling some ideas and you bounce back and forth, and you very quickly can start to move towards um a better solution, and because you're it's in the hyper collaborative. Um, and the same thing with the paper test, right?
SPEAKER_00You know, oh that's weird. Let's draw a screen together. So where do you think that should be? Oh, that should be over here. Cool. Well, here's an alternate version of that screen now. How about that? Um, and that's you know, that would have taken 30 minutes in code to get that to work and test and render through, but I can scribble that in you know 60, 90 seconds. So there's a lot of benefit to being able to do something like that, especially and not just with with end users, but even in inside the team. Um one is and if you have a design system, this becomes a much, much more powerful flow because you've solved what a button is, what did that, you know, all these pieces, all your components are solved, or most of your components should be solved.
SPEAKER_00But um you can say, hey, we're just gonna scribble this up on the board. Step one, step two, step three, everyone's looking at it. They know what those pieces are, because they're we're referencing an established system we're all using, and then everyone can just go and build it. You don't have to sit there and spend a lot of hours like, oh, let me go make perfect mock-ups now, because it's like, nope, we we got the flow, the flow is the important thing, and if if we're missing a component now, I need to go and go through whatever governance we've set up on how to request a new component or set a new one up, even if it's only like a four-person team. You should have those rules of when we add new components, otherwise you'll end up with chaos.
SPEAKER_02So I'll make a statement uh connected to something you kind of alluded to earlier. Um anybody carrying out design work is a designer in in a sense. Yes. Um, and so if you're if you're building a feature, you're designing the feature, whether consciously or not, whether you consider yourself a designer or not, you are a designer doing design. Um and I think it's very easy for designers to unwittingly bullshit themselves.
SPEAKER_02Um like we were talking about AI pre-show, and if you ask Claude to make you a nicely designed page, it'll do it and it'll show you something that like if you just glance at it without thinking of it, thinking about it, it plausibly looks like a good professional design. Um, but then if you actually like start to interact with it and scrutinize it, you realize it's garbage.
SPEAKER_02Um, and the reason that it can trick you into thinking it's good is because there's all these colors and shapes and stuff like that. There are all these things that aren't really the essence of the design that can trick you into thinking that it's good. But when you have just a blank sheet of paper or just a blank white HTML page with Times New Roman black text on it, it's very stark. There's no colors, kind of like your logo thing.
SPEAKER_02There's there's no colors, there's no shapes, there aren't any of these um, there aren't any of these other elements that can trick you into thinking you're making something good when you're not making something good. Um and and I'm a big fan of doing that myself. Uh usually for me it's like just a blank HTML page with text on it. Um because again, it's just the text and that's literally it.
SPEAKER_02And if the text does the job, then it does the job, and if it doesn't, it doesn't, and that's the only thing that's there. And so it has to work. There's no way to like pass the test unless it actually works. And then after you have developed a design that works in that stark format, then you can add on the the colors and and other layout and stuff like that, which aren't just window dressing, those are design solutions to design problems.
SPEAKER_02Um but they're not they're not the essence, they're they're more um they're not as central to the main design problem. So I wanted to say that about the value of starting off really, really stark.
SPEAKER_00And and I think that applies um not just in in um in in apps, but also marketing sites, right? If you start with just your copy, because at the end of the day, especially on a marketing site, right, the copy should be the number one most important thing. And this is why just if you throw it into claw, you're gonna end up with with crap. I've I've tried for years now to get it to come up with good copy. And and there's some skills that help you get better and better, but I don't know. Then you look at stuff where I I've had friends that have worked with with people like Liana Patch and stuff like that, and you just get this amazing stuff that you're like, there's so much personality there, and like it can try and copy that, but like like I had it at one time I threw I threw some stuff in there and I said, make this sound like Amy Hoy, right?
SPEAKER_00My old business partner. I just wanted to see what it would do. And it was going, but it was like it's like it was a it was a poor imitation of of what she actually does, right? Um, so it's it's it'll get you an idea, but again, this is the kind of thing where I think as um as practitioners, we're hyper focused on our own silo. So it'll it'll be really important, you know, about that that my design, my visual design looks good. Then I could, you know, I could be a little less picky about say maybe the the way the database queries are, because that's not my particular strong suit.
SPEAKER_00I'm you know, I'm gonna complain about front-end stuff, right? But I think that's one of those things where we still do need the specialist, and AI is gonna keep saying it can replace everybody, and maybe someday it will, but at least that in the time being, a lot of these things can make experts faster, but they don't replace experts. But back to your um black and white testing, when you're building that HTML page for the first time, only put in the copy and then only do your HTML markup to markup that copy in a hierarchical setting.
SPEAKER_00Very quickly you're gonna start to see, oh, like I don't understand my hierarchy or there's weirdness here or things like that. Because so often we you open up the page and it's just div, div, div, div, div, div, div, right? And there's no high that's zero hierarchy. So div and span aren't inherently bad, they are the least meaningful HTML element usable. And so therefore, they only should be used when nothing else makes sense, or it's purely for presentation purposes. And so a lot of people either flip all the way and say, well, I have to use, you know, semantic tags, and they basically replace divs with uh just a section or something.
SPEAKER_00And it's like that doesn't, that's not really fixing the problem, right? So it's more about looking and analyzing something. How do I do it? And a lot of this is also just the nature of how we build, right? We spent a lot of time building and bootstrap and and and material and these these kind of like, oh, I'm gonna hack all this stuff together to make it workable. So you have these these habits we've developed of lots of divs nested to make rows and columns. You don't need that anymore now with CSS grid and flexbox and things like that, but it's a much different way to think about building. And so this is again where as a designer, I need to understand how grid systems work in the web.
SPEAKER_00I need to understand how flexbox works, I need to know how this can be built, and I need to have a conversation about how it should be built. And this is where design engineers really get underrated, right? That that kind of merger of those two. And then we need to look at it and be able to do a code review and say, no, you've you've gone and done just you know the same thing from a decade ago with Bootstrap, you've just changed it to sections and you're using Tailwind classes now, right? So that's that's the kind of stuff we have to look at and improve. Uh, and because the more the more we move towards that newer CSS style, the more clean our markup can be.
SPEAKER_00That means the more in uh the better the meaning of that content is, the faster it's gonna load, the faster it's gonna render, um, and the more extensible it is. So there's a cool site called CSS and Garden back 15 years ago, 20 almost years ago, but what's so cool about it, they had an HTML page and they had a demo CSS. And anybody could go and make their own CSS and add it. And what was so amazing is the vast differences people came up with just doing CSS changes and just hacking, like here's you like constraints are always, I think, one of the things that make for great design.
SPEAKER_00And that's not just in in visual design, but also in any anything. Having constraints helps you get to a more elegant solution because you have to. Um so looking at that and coming up with with different things along that, it was really cool to see what the power is, and that's that power is still there, but a lot of people have said, well, CSS isn't a real language, or I'm not gonna deal with that, or blah, blah, blah. I don't that's that's for somebody else to learn. And the reality is, is like, no, that's very important part of how this thing is presented. And if you say, Well, I'm gonna build the you know the back end and then we're just gonna like do crap on the front end, okay.
SPEAKER_00So you put up a steel structure and then hung tarps off of it. I mean, what's going on, right? Like, you know, this is this this feels like we, you know, you've got something super sturdy in the back here, but we just kind of said, Yeah, whatever there. And that it well, it it it it doesn't work in in the sense of how the building is anticipated to work or how people want to use that structure. And the same thing is true with our products and our sites. So it's very important, I think, to to be able to go in there and and understand that stuff. Again, you don't have to be the expert in CSS, but you have to know what CSS is capable of.
SPEAKER_00You also have to understand the basic foundations of why we write things the way we do, why we mark things up the way we do. And these are all, I know people get annoyed with this stuff, and I say this in like a broken record, but all this stuff is the basics of accessibility. And accessibility is not just a blind person. There's there's various temporary accessibilities. So somebody who's got cataracts, somebody who just had eye surgery, somebody who's in bright light. These are temporary vision impairments. Um, and then you have things like, you know, I wear glasses. So if I'm, you know, if I take these off, the screen's a little blurrier.
SPEAKER_00You know, something as we age, right? You know, the that super small text isn't workable anymore. We're gonna have to raise that font size. How does the page change when we do that, right? So these are you could be drunk or um I see four of these. What's going on with my phone? Um, but is this gonna work for me when I'm on LSD? Right. Anything. I mean, if you we can you could you could theoretically come up with almost any numerous kind of things that would be uh that that accessibility helps solve, right? I don't think it's it's fine. I don't think we want to call them. I mean, people would refer to them as impairments, but the important thing is that there's states of being that we need to solve for to make the product more accessible.
SPEAKER_00Um, and and that applies to to almost everything. And so being able to think about those things and then say, hey, you know, I've got this, you know, AI gave me all this cool motion. Look at all this animation it did for me. Well, do you have a preferred reduced motion setting in your style sheet? Because some people that really is difficult and painful to look at. Do you have a setting for that? No? Hmm, okay, please, let's revisit that. So it's it's being a little more holistic in how we think about these things.
SPEAKER_00And if you start with that core that everything works when it's just black and white, then you're it's we call progressive enhancement, right? So I'm adding features and functions that make things nicer, but don't affect the internal functionality of stuff. And this is one of my biggest complaints about React, honestly, is that React breaks unless you're using React, right? I mean, it does like it does not degrade to server refreshes, and and almost all the JavaScript single page things like end up in this way, like it has to work that way. A lot of people will use React and they don't necessarily iterate the URL forward, so the back button is sudden suddenly broken.
SPEAKER_00Um things of that nature. These are you know common things I've seen over 15 years. So make it work boringly, and then you can make it fancy schmancy.
SPEAKER_02Yeah, I couldn't agree more with that. Um another of my pet peeves with uh you know JavaScript framework built sites is like middle click to open in a new tab doesn't work in a lot of these sites. Um that is a big pet peeve of mine. Um and it's like these like web standards and conventions that we've had for decades now, like they should work.
SPEAKER_00They should.
SPEAKER_02Yeah, and and for for me personally, uh I use like JavaScript as a last resort, not as like a fundamental ingredient in everything that I that I build. And that makes, you know, both from a software maintenance perspective, it makes it cheaper to maintain, but I think it's also better for the user, again, uh make things work in in the barest way possible, and then add fanciness onto that afterward.
SPEAKER_02And and stuff like all right, I'm just like a curmudgeonly old man uh and I hate everything. Like, animations, like it's like, all right, that like cutesy animation was entertaining the first like 40,000 times I saw it, but like I just want to click the fucking button and see the thing that I want to see, you know. Like I don't want to have to have like a 300 millisecond delay between when I tell you that I want the thing and I get the thing. Like I just want to click the thing and get the thing.
SPEAKER_02So like no thank you to though all those animations.
SPEAKER_00And there's a there's a balance, right? I mean, there's there's some um one, what's great is that most of those animations are now doable in CSS, so you're not doing weird JavaScript anymore. And so then you can address that with prefers reduced motion, right? So you could you you're putting the power back in the hand of the user. Also, there's there's good hinting where I click a button and a panel slides in very, you know, but it doesn't have to take, it doesn't have to be like a slow slide in, right? This isn't like you know, it could be like a and it's just it's like, oh, it's gonna catch your eye, that's where I need to go. So there's there's hinting like that, pardon me, that that really help uh and you end users understand and flow through the system better.
SPEAKER_00But then, you know, people take that overboard and it's you know it's it's like a a dancing clippy driving you insane, and you're just like, I just need to, I just need to click this button, man.
SPEAKER_02Yeah, and I have a hunch that a lot of that is driven by like there's a programmer or a designer, and they're thinking about the presentation where they show it to their coworkers and bosses and stuff, and they they show it off, and everybody's like, oh, that's neat. Hey Jimmy, look at this uh thing. And it's like cool in that setting where everybody has to see it like once or twice, but then again, for the people using it all day, every day, it's a mismatch for their usability needs.
SPEAKER_00Yeah, and I mean this is this is part of the siloing issue that I think has been an issue too uh recently. Like, you know, you have motion designers. Well, if you're if you're would would a motion designer want to go in and say we need less motion? I mean, really good ones would, but it's kind of like saying, you don't need me. Um, you know, um, and so there's there's a part of this like over-specialization that happened over the past decade, and AI is actually kind of nuking from orbit in an interesting way, is that you know, people got really specific about what they could do.
SPEAKER_00Um, and in a really big team, that makes sense, but in most most instances, you you know, a good generalist that understands there's some basic motion moves that make a lot of sense and we'll use those in this way, and then we'll have an alternative for people who don't want it. Or likewise, like, oh, I know that these basic accessibility rules are there and I know how to check them. Um, you know, if you're Google, you're gonna have dedicated accessibility people, and that's great. But most companies can't afford that. They may get a contractor in to help them do an audit, but you know, in general, we should be teaching everyone the basics. So nothing is shipping that bails WCAG 2.2AA.
SPEAKER_00Like that should just be uh, this is how we build software. It's almost like I mean, it's unfortunate that we've had to get to lawsuits. We've had we have all these rules, and and there's not really an ADA equivalent. Section 508, if you're working in federal or or or state government stuff, but um, you know, now unfortunately we've had people had to get sued for them to make the changes, right? So, like the Domino's case is a famous one, right? And some of this is ambulance chasers, but at the same point, it's getting uh visibility onto what is is a desperately needed thing. We we need to make things accessible as just par for the course.
SPEAKER_00That's like that is table stakes to ship software today.
SPEAKER_02I I also feel like Domino should get sued for the quality of their pizza. Um yeah. Um okay, so we should probably start heading toward a a conclusion soon. Um but anything else that you want to touch on that we haven't talked about yet with regard to usability or just just anything at all.
SPEAKER_00Well, I think the um the one thing that's interesting, and we kind of touched on this in the pre-show, just is the nature of um consulting these days, where uh everybody seems to be in a we're playing with AI, which is great. I'm and I'm playing with AI, right? But uh I feel there's this weirdness that's kind of become a we're waiting for the pendulum to hit the end and start coming back, where people are like, I don't need anybody, I'm just gonna do it all with AI. Um and some of this is people just learning the hard way. They don't want to listen to other people tell them that, well, this is what's gonna go wrong for you.
SPEAKER_00Um and we've already seen this with um with with certain companies that went and vibe coded something and came back and said, Nope, that didn't work at all. Um and I'm I'm a firm believer that most of this stuff amplifies what's already there. So if you don't have any idea about how software is built or how software should work, it's very difficult to ship software. Um yes, Claude Claude or ChatGPT or whatever can walk you through how to deploy software and probably even get you set up on DigitalOcean and running all the stuff, and there's lots of ways to do that, or Heroku, or Hatchbox, or any of these tools.
SPEAKER_00And the downside is that you then don't realize the life cycle. We've lived a life cycle, right? Getting paged for you know, something's down. Oh, is that really down? Is it just a false alarm? What's up? Or you know, something where it's it's like I've got a memory issue and something's really slow. It didn't happen in development, but when I threw 100 users at it, all of a sudden now there's a problem. How do well, where do I even begin? Um, and so that's the stuff that it just makes uh experts faster to find the problem. Like, hey, look at this, you know, hey, I'm looking at a new code base because I just got brought on this project.
SPEAKER_00Tell me, tell me the good, the bad, and the ugly, right? And and that's that's been really powerful for um for a lot of things and and and not especially the things we do all the time. So I did something with static analysis, I built a uh gem that's up on RubyGem, UI Guard Rails, and it uh it basically goes through a Rails app and looks for um repeating patterns as well as uh accessibility violations. It's the stuff that I do on every single tool that I open up. And so instead of running burning tokens, I just run this this gem, and now I can also make this gem part of my CI pipeline, right?
SPEAKER_00So now every time I make sure I'm shipping, I'm not shipping accessibility issues, right? Or at least the basics. There's probably some some extraneous stuff that I might miss, but I I've got a much higher level of confidence in what I'm pushing to to get. So there's the that's the kind of thing. But I think, yeah, everybody's trying to figure it out, and I'm waiting for the pendulum to swing back and see when people realize, oh, I can't do everything by myself, you know. And unfortunately, I feel people are gonna have to get get bitten a little bit. You know, the person who's like, Oh, I can make all my contracts with Copilot or ChatGPT when they they realize that it was not even internally consistent with itself and they've got a you know, they lose a lawsuit, then they're gonna be like, now I need to hire a lawyer.
SPEAKER_02Yeah, um I've seen similar things. I haven't done consulting myself for over a year now. Um, but I I talk with other consultants and stuff like that. Um and and there are overlaps in the consulting market and just the job market for full-time employees too. Right. Um, and I kind of get the sense that people aren't as eager to hire these days because the thought is like, well, if we want more bandwidth, we can get the bandwidth from AI rather than from more headcount or from hiring consultants and stuff like that.
SPEAKER_02Um, which is an understandable perspective. Um, not wrong either. Yeah. Yeah, and I think the question is like, um, what is a consultant who is looking for work to do about that? Um and it seems like a lot of people had the idea, um, myself included, although not really anymore, when the AI wave first started to hit, uh people got dollar signs in their eyes, and they're like, Oh, I know what I'll do, I'll be an AI consultant.
SPEAKER_02Right. But now there's like a bazillion self-styled AI consultants, just kind of generally, it's like, what do I do? I help you use AI. Yeah. And it's like, all right, well, anybody can claim that. Um, and so I think that's kind of a tough uh niche to occupy um because you're competing a bunch of other people who are making the same claim.
SPEAKER_00Um and it's so new, there's no, I mean, how do how do you, as an end user purchasing that service, how do you know this person is not full of it? Because everybody, you know, you if you spend any time on on X or any of the systems there, like and you like my feed is very filtered down to a lot of AI stuff. Every day somebody's like, I've solved this problem, or Chat GPT is so over, you know, and you're just like eye roll, okay. You know, you know it's you know it's BS hype. And you know, the the people who are building building are usually like, hey, I've got this cool thing you should check out.
SPEAKER_00You know, it might solve your problem. And that's those are the people that are actually doing really inventive stuff. Like I got two friends in town, um, Andrew Boyd and Justin Schrader, and they're doing a thing called standard agents, and it's super cool. And it's this this kind of how do we turn, how do we make this kind of a replicable tool where you can actually deploy agents and it's not like, oh, well, install open claw and figure it out. No, that's that doesn't work for most companies, right? So, but they're they're actually chasing something very intentional and and you know, working through it, and it's not this like we've solved world hunger, you know, everything sucks except our product, and that's what you know.
SPEAKER_00That's you you see you've seen these tweets and you're just like, oh god. Okay, right.
SPEAKER_02Yeah, um, and I'll I'll to make a brief aside. Um, a few years ago, uh I was working on on uh carving out a path for myself as a consultant, doing not like hands-on labor, but doing advisory work. So the format of that was oh yeah, and you were a client of mine. I I kind of forgot about that. Um yeah, um, so when you and I worked together, we had a series of calls.
SPEAKER_02I never did any work for you. Um it was all advisory. We looked at your uh code together and and we talked. Um, and that was the service that I was providing. And with other clients, it was it was even more um toward the abstract end of the spectrum where there was no screen sharing or anything, we were just talking. Yeah. Um and I think that that can be a great way to move up in value because if you're doing implementation work, there's a lot of people who can write code, you know, and you can you can claim that if you hire me, it's a hundred times more valuable than hiring some other person.
SPEAKER_02And I really do believe that's true. Like if you hire if you hire me for a weekend, I'm not gonna create a hundred times as much value as as somebody else. But if you hire me for a year, I most certainly can create something that's a hundred times more valuable or a thousand or ten thousand times as valuable as something somebody else might build. They might build you something that's hardly even, there's hardly even any value at all. You might have to throw it away.
SPEAKER_00Yeah, it works, but right.
SPEAKER_02But like what about from a business perspective? Is this gonna is this gonna generate uh revenue for you and stuff like that? Anyway, um, because there are a lot of people who can write code and there's not a lot of uh perceived variance in the value of of that service, you are subjected to uh market pressures, and so if you charge something that's like I I don't know, uh if you if you charge something that's outside the range of perceived market rates, people are gonna ask why.
SPEAKER_00Yeah.
SPEAKER_02Like I remember uh ten years ago, I was trying to raise my rate from a hundred bucks an hour to one fifty and I would talk to clients and and there was like I was like just outside that perceived range at the time. People started asking me, like, okay, well, I pay my other guys a hundred bucks an hour, why should I pay you one fifty instead of a hundred? And at the time I didn't have an answer. Um, but if you provide a different service altogether, then you can get away with that, and you can say, Well, I charge this many thousand dollars a month for having advisory calls.
SPEAKER_02People aren't gonna compare that to a hundred bucks an hour commodity coding because it's not commodity coding, it's a different service. Anyway, all that is to say, I started going this other direction of advisory work. Um and I never could figure out exactly the right kind of the right kind of services to offer and to who, because that's a big part is the who, you know, who who am I?
SPEAKER_02Right. Um I found a lot of people who like they didn't have like uh well they didn't have like Fortune 500 level budgets. And so it's like, all right, this is okay for like somebody who wants to have like one call a week and stuff like that. I can get a a good rate that I like out of that, but I can't make a whole living if I can only find like five or ten clients who want to do this. Um and so who do I offer a service to who can afford it, who finds this thing valuable?
SPEAKER_02I never did figure that out. Um anyway, I've long since lost whatever point I was trying to make. So I'll pause there.
SPEAKER_00No, I th you had a couple of great things in there I wanted to touch on. One is the hourly billing is nuts, as so eloquently put by Jonathan Stark. Um, and and it's um it's something I've moved away from because it and this is um when I worked with Amy Hoy, like I was charging 75 bucks an hour, and and right out of the gate, you know, we started up hyphenated people. She's like, we're gonna charge 250 an hour, and I like choke on my coffee. I'm like, no one's gonna pay us that. She's like, watch and learn. And sure enough, boom, went out and did it. So I I did learn a whole lot in in how you position and it changed the clientele entirely. The people at 75 an hour and what they expected, totally different ball game than the people at 250 an hour.
SPEAKER_00And there was a lot less pushback, surprisingly, at 250 an hour. People were like, I'm paying for super expertise, I just want you to execute and go. And it was incredible to see that difference because at the time I didn't realize that even that echelon existed. Um, and so being able to sit there and run at that level all of a sudden you're like, okay, but then also you're sitting there and people are arguing with you over, well, that's so much an hour. Well, you know, I can pay somebody a hundred an hour and get, you know, that. And it's like, yeah, okay. So do you is this a math problem? Do you have a problem like where you want me to charge a hundred an hour and multiply it by 2.5 and and solve these things super fast?
SPEAKER_00Because the the reason you're paying me a much higher rate is that I've done this for a long time and I've seen all these problems. This is very little is new under the sun. And so I come in, I see this thing, and I'm like, oh, we're done. Here's the issue, here's the execution, go. And that was 30 minutes. You get somebody who's a hundred bucks an hour, they may not have run into this problem before. Maybe they have, but you know, you're gonna end up probably paying the same or more in some cases for the same outcome or a similar outcome, or even not the outcome. So that's always something where I just kind of start stopped arguing that and said, look, I bill flat rate for a project, or I bill monthly retainer.
SPEAKER_00And I think that has that makes it a lot easier because now we're not sitting there arguing, like, well, how many hours am I getting? It's not, it's not the attorney thing and what I'm bearing, you know, what's your blended rate? What's the paralegal build at? What's this guy built at? You know, I don't want my partner time because that's 500 bucks an hour. You know, I just want the paralegal to look at this, right? So, I mean, that's you get get through all of that and you spend a lot less time arguing accounting, which nobody really enjoys doing anyway. We want to solve problems, not argue over, you know, zeros and ones on a spreadsheet. So that I think is a super important thing for people to think about is is that.
SPEAKER_00And then also your perceived, like, what is the value of the problem you're solving? Because some pro you could do the same amount of hours for a company and one of them provides a hundred thousand in value, one of them provides two thousand in value, but it's the same amount of time. So being able to look at that and analyze that and say, oh, you know, I don't even want to touch that project. Um, and this is something uh I Dan Muller is my business coach, and this is something I've learned from him. It's really, really valuable is like being able to say, What's the what's the important part here? What's what's the where where can I really make an impact?
SPEAKER_00And it may not be what they even contacted me about. It may be something totally different where we're like, oh, you know, this thing over here is so much more important for you to move the needle, and you're gonna get a much better return on investment for the time we're gonna spend on it, you know. And and sometimes they're like, well, that's not what we want to work on. Okay, well, we've called it out, we've told you where we think we should we should approach. So that's I I think there's a couple different ways like that. And then I think also you were right with the the kind of advisory thing, you know, I've I've been working with cyber maniacs, my friend from from Catholic UK.
SPEAKER_00Um, she and I know each other for 25 years now, whatever. It's a long time. And um, so when I when I uh left Powerfleet in 2022, I just kind of started chatting with her and have been working in that kind of broad design development advisory thing. And sometimes I'm jumping in and getting my hands dirty, and sometimes it's just like we're having conversations about, oh, this is how we should move this forward, or I'm reviewing things that that contractors are doing, you know, sometimes helping interview things like that. But there's a lot of that kind of like I just have this really broad expertise, so I can come in and apply and help her be more confident in the decisions they're making at that at that company, and uh and you know, help move the the ball down the field that from like okay, here's where we're trying to get to.
SPEAKER_00You know, yeah, yeah, we can do that, but you know, this is more important over here. So I think there is a lot to the advisory thing, especially in if you can find the right matches and the right personality fits where they trust your. judgment and have you have a need and and those things aren't quick turns you don't just send out a blanket blast let me be your design advisor like that's something where you have to establish over a very a long time either through that they've they've seen you speak or they've they've talked to you or you just know them from from the community and you've you they've seen you've seen each other's work over 20 years and they're like oh I'd love to love to have you come in and look at this and sometimes that also just like yeah we're gonna use AI first and that's cool because you know hey then then we're actually tackling harder problems like if I come in and just say here tackle all this easy stuff okay well yeah but if if you can actually get past that and then we're now looking at like actually more serious problems there's much more value in those and in and my rate for you you know if uh looking at those kind of things so um I think it's just a matter of changing like if we think about from you know the traditional offer ladder we used to see in in consulting right like that lower level is kind of going away and being replaced by AI and that's not a bad thing.
SPEAKER_00That's just saying that we need to now change how we approach what we're selling and what we're we're offering to people and and and finding a better value that starts at a higher ticket price but also has a better value outcome right you're not we're not just saying okay here's my$500 audit and and it's something that AI is going to give you for you know five bucks in tokens right so that's that's I think a a big change that we're seeing in in the kind of the consulting flow. But go ahead.
SPEAKER_02I'll I'll share something else too um you know there's all sorts of things I I've always been very interested in just like understanding the world um and sadly this has led me to learn a lot of things I kind of wish I never knew um something I've learned is that like I I'm not sure if this is exactly true but like the vast majority of the economy is total bullshit yes um and it's it is kind of a bummer when you you yeah that I remember that you're just like what yeah yeah because it's like uh we we get paid these sometimes huge amounts of money to do things that don't need to be done and like you're familiar with this uh in in like the freelancing advice market um there's all kinds of people um shilling advice on things they've never done and the people buying the advice don't use it yeah it's like what there's nothing happening here like this is fake advice bought by fake freelancers there's money changing hands but nothing is actually happening it's fake um and like I don't know what percentage of the information economy or knowledge worker economy whatever is that but an appallingly large percentage of it and so a lot of the uh consulting engagements that I've done over the last um 20 years um have been some form of that you know it's like I want to use this screwdriver to drive a nail uh help help me figure out like how do I hold the screwdriver best to drive the nails no well what you want is a hammer it's like yeah but I like I don't have time for a hammer like I don't really like hammers.
SPEAKER_02Like I just want to get this nail driven with a screwdriver and it's like okay that's what you want uh we'll we'll do that.
SPEAKER_00Yeah. And I've I've now tried to be more like well you probably want somebody else like and it's hard to do that. It's so hard to sit there and turn away work especially when you know if it's a light season or or there's a running joke that uh you know oh my God is my business ending or is it just August? Like every year there's like that that dip in the summer because everyone goes on vacation or projects slow down and then you kick up into the fall and it depends on fiscal years too but like there's that end of the year push to make sure you've got the budget spent as you go into the new year and you get your new contracts happening and this is so it's it's always this fun like I was joking with a bunch of people about that and it's like uh panic no okay it's it's just August and you look back you know if you can look at your historical records you're like yep but yeah no there is a lot of that and there's one there's one that I'm guilty of too where I I'll buy a class that I actually want to take and then it just sits there.
SPEAKER_00And by the time I get around to it I'm like oh this is out of date now right and so um it's it's this this or this thing of like I just need more training before I can start that's that's something I have to force myself out of where it's like no go stumble go fall the best teacher's experience right and so like get get the bare minimum I need and then test because I this I don't I'm I'm not very comfortable in sales. That's something I have to force myself to be better about and like mentally say nope I can do sales right um and it's it's just a a mental hurdle I've mentally had for my whole life and that's just one of those things that's a self-inflicted hurdle.
SPEAKER_00It's not true. Because I can look back and say no if I get an introduction I'm fine I'm I'm off to the races. And so what I'm actually uncomfortable with is being told no and so I mean there's then you hear every salesperson talk about like you get 10 no's for one yes or something to that effect right so it's just like I just got to be fine like and no is not a reflection on me. No is a reflection on viability of the offer to that person. And that that was another thing that that helped me you know working with Dan just like okay yeah there's not it's they're not saying no you suck.
SPEAKER_00They're just saying no that's not something I need right now. Oh okay that you know and it and it sounds so simple but it's also one of those things that you know it's it's it gets it gets harder as that gets it's been ingrained in your mind for a long time you have to kind of break through some of that. But again I think if we are we were looking at the the modern consultant it's it's uh it's definitely shifting and we'll see how we play out.
SPEAKER_02And um you know never in the history of the world has anyone bought anything because they need it. They only buy it because they want it. Yeah they may they might want it be and you know you don't need anything you don't even need food uh because you can just like not eat anything and then you'll die but like that's pretty dark but yeah but it's just you don't you don't need to be alive you know um so there's there's really like no such thing as a a need um and people uh peop people don't want the things that you might want them to want right um like I want people to want to drive nails with hammers and not screwdrivers but 99 out of a hundred people might want to drive a nail with a screwdriver um and it's so prevalent that you you can't believe it's true.
SPEAKER_02It's like really 99 out of a hundred people want to drive a nail with a screwdriver and not a nail and it's like yeah that's really the way it is and so you have to um you have to sell bullshit uh which is a very tough pill to swallow um because it's like I don't want to help people do things that they shouldn't be doing. Right. Um but like if you want to participate in this economy you have to again help people do the things they want to do not the things you want them to want to do.
SPEAKER_00And sometimes it's the hand wave right so okay 99 out of 100 want to drive a nail with a screwdriver. Well you know what I'm gonna take a screwdriver and put a hammer on the handle. Here it's a screwdriver and you use it this way when you've got nails and use it this way when you've got screws. Oh that's amazing I'll pay millions of dollars for the thing right so there's it's always this like okay if if if I've got to meet you where you're at sure let's play the game and see what I can come up with. And again this is where this is the whole design is uh empowered by constraints not the other way around right uh I think the the best design solutions come out of super weird constraints and sometimes I'll even make them because I don't have enough and it's like it's really like that blank page is the worst nightmare for a designer.
SPEAKER_00Because I where do you begin? Okay well let's start give me some constraints let's lock some things in so I'm working on a much smaller scope. But yeah I think there's there's always opportunity to find those challenges and be like oh we're gonna turn this on its head and see if that's and maybe maybe we we put that out there and everyone like sees it for what it is. They're like well that's stupid. Why don't I buy a hammer and you're like exactly but you know I mean at least it's worth a shot and maybe it becomes a super successful thing. There's so many products out there where you're like that sells okay all right and now let me let me figure out why that sells what is that what is that connecting to and it is often you're right that emotion people are buying on the emotion or the removal of pain.
SPEAKER_00There was a great example I just saw somebody talking about where they were selling an AI bot to do X, Y, and Z and you had to set it up and coordinate it and the person was like I will pay$25,000 to never have to touch this thing and it's like there's you know everyone like wants to build this the next product that gets bought and gets sold but sometimes a servicesorg is the best solution for that just be like we remove this from your you never have to worry about this again. We we take care of this for you. There is no good way to do this without manual interaction and we're gonna make that manual interaction happen at an affordable rate to get you this get you your time back right so that's you know buying back your time is something a lot of especially entrepreneurs and business people the higher up they get in the ladder that's something very important.
SPEAKER_00They don't want to spend the time doing it. So finding the way where we can angle in is always important to understand and say okay here's here's something I think that you would you would uh benefit from and it's not going to cost you that much and you're gonna get a lot of value out of it and what do you think? Um and it's it's such a weird thing.
SPEAKER_02I mean I'm I'm so used to the more formal I mean this is the downside of coming from architecture is you write 400 page proposals on a building right and that is and and in design agencies do this too here's this huge capability stack and it's like no it's like send a send a really quick person little message and it's like what what so that's something I've had to had to learn you know in the last year in in in Dan's program just to be like okay that that does work in a weird way okay well we are really running out of time now so I'm I'm gonna ask you the final question of the session which is uh is there anywhere you want to send people to learn more about you and what you're up to?
SPEAKER_00Yeah so um not too much gets posted there but if you want to see about the farm you can go to Sfamato S F U M A T O farm dot com um and uh and then for consulting or any kind of things along those lines I'm starting to rewrite the Rails view which is the book I did years ago I'm starting to do it as a series of articles and that's all going to be on meticulous.com which is also my consulting site. And and then if just personally I've got you know a lot of my old uh conference talks and things like that up at jonathaid.com so J O H N and then A T H A Y D E dot com.
SPEAKER_00So you can follow me you know any of those places and some of the socials I'm I'm intermittent on a lot of the socials but uh but hit me up and say hi and love if you got a problem love to talk about it.
SPEAKER_02All right well we will put all that stuff in the show notes and John thanks so much for coming on the show. Thanks Jason
In this episode I talk with Joel Hawksley, Staff Software Engineer at GitHub and creator of ViewComponent, about whether AI is making us dumber, why blocking code reviews struggle under a flood of AI-generated code, and...
In this episode I talk with Riccardo Carlesso, Google developer advocate and co-founder of Rubycon, a Ruby conference held in Rimini, Italy in May 2026. Riccardo explains how a joke about PyCon became the conference's...
In this episode I talk with Travis Dockter, organizer of Blastoff Rails in Albuquerque. When Sin City Ruby and RailsConf both ended, Travis decided to start his own conference. We discuss how cheaply you can run a...
In this episode I talk with Julien Danjou, CEO of Mergify, about merge queues: why PRs that pass CI separately can still break main together, and how testing changes in a queue keeps main green. We discuss how Mergify...
In this episode, I talk with Kevin Dias about his journey from investment banking to programming in Japan, building Ambiki for speech language pathologists, and tackling feature requests with a problem-first mindset....