Allison McMillan - Designing Serendipity

Allison (clip): People that I've talked to that have very robust agent or agentic orchestration are the people that really do very much the same thing every day.

Jeremy & Jess (intro): Hey everybody, I'm Jeremy. And I'm Jess. And we're two developers, business owners, and friends exploring the world of independent business and Rails. Welcome to IndieRails.

Jeremy: Hey everybody, welcome back to another episode of IndieRails. Today we have a special guest, Allison McMillan. Allison is a consultant, organizer, speaker, and podcaster.

Jeremy: She founded Tavlin Consulting, where she helps organizations build high-performing, well-managed teams. Allison is a former director of engineering at GitHub and a former board member and president of Ruby Central.

Jeremy: She facilitates workshops, off-sites, and conference experiences. And she offers services as a fractional VP of engineering, as well as advisor and mentor. Allison, thanks for joining us.

Allison: Yeah, thanks for having me.

Jess: Hey, Allison.

Jeremy: So I've been following you online for a while and I've gotten to meet you maybe a couple times, but this is partly an excuse to hear your story.

Jeremy: And, you know, like you as a consultant now, I'm really curious to hear how that's gone for you over your 20-plus year, 25-year career.

Jeremy: But maybe before we get into that, like, is there anything I've left out, like, of what you're doing these days? And maybe tell me a little bit about what you're about.

Allison: Yeah. Yeah, it's funny. My career has had a very windy path.

Allison: And so I feel like I've had, you know, like my career has had nine lives and I keep regenerating or, you know, like innovating on them.

Allison: I think that you gave, yeah, a great introduction. I think, you know, in terms of, like, Ruby and Rails is, yeah, on the Ruby Central board. I was also on the Ruby Together board.

Jeremy: Oh, yeah. And

Allison: now I'm currently on the WNB.rb board.

Allison: So, you know, it's being a part of the Ruby community and, you know, helping with that is a key part, something that I love doing as well.

Allison: So, yeah.

Jeremy: That's awesome. Okay. So, you've been a longtime Rubyist. Take us back.

Jeremy: Like, how did you get into development in Ruby and how has that led to, you know, to today?

Allison: Yeah. So, I actually started my career as in the nonprofit world doing leadership development. So, yeah, totally, totally different world, totally different thing.

Allison: I started there. Then I had an idea for a startup. I did it sort of, like, nights and weekends. And I was looking for a technical co-founder.

Allison: And everybody was like, yeah, you and everyone else. And so, I, you know, I was gathering, like, okay, what language should I build this startup in?

Allison: And how do I make myself and this company sort of interesting for a technical co-founder?

Allison: And one of the suggestions that I got was to go to some of these technical meetups and actually learn, you know, learn more about that world. And so, that was when there were Rails Girls happening everywhere.

Allison: So, I went to a Rails Girls here in D.C. And I started going to Ruby meetups because that was sort of the number one suggestion was, like, build your startup in Ruby. That's cool.

Allison: And then, as I was there, like, I just got very, very interested in the actual programming aspect. So, I was sort of looking for a technical co-founder.

Jess: You drank the Kool-Aid, huh?

Allison: Yeah, right, and learning and building. It was also around, like, when boot camps were sort of starting.

Allison: And so, it was actually when most boot camps, like, still posted their entire curriculum online. And so, there was a group of us here in D.C. that were, like, let's just, let's do a weekly meetup.

Allison: Let's, like, gather some mentors and let's, you know, teach ourselves how to code. That's cool. So, we did that and, you know, would, like, co-work during, like, before the day of meetups.

Allison: And, you know, there were a few folks in D.C. The D.C. Ruby community was really awesome. So, you know, would read over our code and help give us tips, tricks, et cetera.

Allison: So, that was sort of how, after about a year, I shut down the startup and went into being a full-time software engineer.

Allison: Did that for a handful of years and then went back into leadership, right?

Allison: So, engineering management at GitHub, which is where I sort of started, got to pull my software engineering experience as well as my pre-tech experience, right?

Allison: From nonprofit world, from leadership development.

Allison: And then, through that, right, like, my professional journey was when there were reorgs, sort of getting to manage, like, different problems, different teams, et cetera.

Allison: The off-sites thing, I mean, I've been facilitating these experiences for now for 25 years.

Allison: But when I went into engineering leadership and was responsible for putting together off-sites for my team, people would walk away and be like, I didn't even know that an off-site could be that, let alone, right?

Allison: And so, it just sort of, like, I ran, I remember I ran one virtual department off-site during COVID.

Allison: And the feedback that I got after, you know, through survey forms, et cetera, was, like, that virtual off-site was better than, like, 75% of in-person off-sites that I've ever had, right?

Jeremy: Wow. Yeah.

Allison: I mean, and that's just, like, it's, like, one of my favorite things to do.

Allison: And so then, yeah, so a couple of years ago, about three and a half, four years ago, I just started thinking about what are all the experiences that I've had? What has made a difference?

Allison: What are from this twisty, you know, career path?

Allison: What are the pieces that I can sort of pull together that feel, like, a niche, that feel interesting, that feel unique, that feel really valuable?

Allison: And that is kind of, like, how I, at least how I started, how I started my business.

Jeremy: That's awesome. Was there, like, I'm curious, like, okay, so you've had multiple, either director of engineering, head of engineering, VP of engineering roles.

Jeremy: Was there a transition into, like, starting to do some of that fractionally and then realizing, like, maybe I should turn this into a larger consulting, like, this is what I'm going to do now.

Jeremy: Or had you identified even, like, in your last full-time role, I want to go consult, I want it to look like, or I'll figure out the services as I go. Like, what do you think, how did that happen for

Jess: you?

Allison: Yeah, I mean, I think, you know, I found that regardless of what, and this is, people always ask me, like, what vertical do you operate in, what industry, I find that at a certain place in time, at a company, they tend to, like, hit the same roadblocks and barriers regardless of, regardless of, like, what industry they're in or what place they're in.

Allison: And I found this, you know, even at GitHub, which was a more established company, right, the kinds of problems that I was solving, the teams and departments that I would be brought into were really very similar.

Allison: And so, when I thought about, okay, if I want to start my own business, what kinds of services, what does that look like?

Allison: I realized that there is, and there are a lot of people that do fractional work, and even a few years ago, there were fewer people, but there were a lot of people sort of getting into it.

Allison: And so, recognizing that for a company that doesn't need a full-time person yet, right, either they don't have the budget or they don't have the scope, but they need someone who can solve these sort of, like, higher-level management problems, these milestones they're reaching, these barriers that they're hitting, that I could do that, and I don't have to be there full-time in order to do it and in order to be effective at it.

Allison: The other thing that I thought about when I thought about starting my own business was, what are the things that I love doing, and what are the things that I dislike doing?

Allison: Or not that I dislike doing, but that I feel like I'm a big, big person on, like, do not waste my time. Like, I do not want to waste your time, and do not waste my time.

Allison: And so, as I was thinking, it wasn't necessarily, like, the things that I dislike doing, but maybe the things that I feel like are not a super valuable use of my time in order to accomplish the goals that I need to accomplish in the role that I'm in.

Allison: And so, when I thought about that, right, like, off-sites, man, do I love, like, designing and facilitating off-sites in ways that are, like, bespoke and unique for different teams, and in ways that, like, just, like, blow their mind, right?

Allison: That a lot of, especially engineering teams, like, just don't get or have that experience very often. And so, I was like, okay, I want off-sites to be part of it.

Allison: And they have, like, a great value proposition, right? You're bringing everyone together. You're spending all this money. And then, what are you going to do? Have them, like, stare at screens or, like, work next to each other?

Allison: Like, you can do so much more than that. So, and then the fractional piece was another.

Allison: It was like, okay, this is the kind of problem that I specialize in and that I solve and that is, like, really my focus. And they are problems that I love solving.

Allison: Like, they're things that I love doing. And usually the person who's in-house does not like solving those problems or doing those things.

Allison: And so, I think that was a big part of it when I thought about fractional or when I thought about these different parts and pieces. It was like, what do I want my work day to look like? What do I want my sales cycle to look like?

Allison: What do I want my contract length to look like? What do I want? This is, like, a spicy one.

Allison: But a lot of people are always, like, oh, you should, like, productize everything so that you can work fewer hours and, like, have more clients. I actually, I personally, I think that's boring to me.

Allison: Like, I like taking, you know, a lot of my workshops, like, they have a similar style. But then I make them unique forever. Like, I co-organize. Like, I make it unique for every team that I'm working with.

Allison: I think that's somewhat the value proposition. And people are like, oh, you should totally just productize that and be like, this is what your three-day engineering off-site looks like. Yeah.

Allison: I don't want to, because, like, I don't think that any two engineering teams should have a three-day off-site that looks exactly the same, that's just, like, off the shelf. That's a spicy take.

Jeremy: No, I hear that. They're

Allison: like, you're silly, Allison, for not wanting to do that. But, right, that was part of, like, okay, what do I want to offer? What do I want my sales cycle to look like? What do I want my contracts flow to look like? What do I want?

Allison: Who do I want my clients to be? Who makes sense as my clients? Right?

Allison: Like, all of those different questions, and that's what led to, like, okay, I want this chunk to be fractional, this chunk to be this, this chunk to be this.

Jeremy: So, you really were, sorry, go ahead.

Jess: I was just going to say, I never thought about that before, but it makes a lot of sense that if you really enjoy doing the off-site stuff, I'm assuming that most companies would probably only do, like, one or two of those maybe a year.

Jess: So, if you worked for a single company, you would only get to do your favorite thing once a year, right? And now, so, you're getting to offer that service to many different companies, because that makes a lot of sense.

Allison: Or to run them within a company for many different departments.

Jeremy: Oh, yeah.

Allison: It's

Jess: okay.

Allison: You know, because then it's, like, you're, and this is, I will be honest, this is a nut that I'm, like, still trying to crack, but I do think there's something really valuable in, like, I help, you know, engineering, and in engineering, like, every team has an off-site.

Allison: I know the company culture, I know how to sort of make it unique for, like, the infrastructure teams versus the product teams versus blah, blah, blah.

Allison: In which case, you're working deeply within one or two companies, but in, again, like, not every team is the same.

Allison: And how every team interacts with leadership and product and gets their work prioritized or not prioritized and how much, like, their software development lifecycle is changing with AI.

Allison: Like, it is a little bit different depending on where in the engineering org you go. So, yeah, that as well.

Jeremy: I

Jess: was wondering, also, you mentioned earlier that you said you find that companies hit this common point. Did I say that phrase right?

Jess: Where they get stuck. Can you elaborate on that a little bit? Is that a company size thing? Is it, like, a company that's trying to grow from, like, 5 to 10 people or 10 to 50?

Jess: Or is it more of, like, just where they're at? I'm sure it's a depends type question, but can you speak more to that?

Allison: Yeah. It is an it depends type question because sometimes it happens at, you know, five engineers and sometimes it happens at 20 engineers.

Allison: But generally it's when at most startup companies, I would say, like, pre-series D, the engineering team is the largest team that exists.

Allison: And it is the highest cost center because not only is it a large team, it is also an expensive team.

Allison: And unlike sales or marketing or some of the other teams, it is also a really hard team to tie directly back to metrics, right?

Allison: Because if engineering ships a feature and that feature does really well, does that feature do well because the sales people sold it the right way? Because the marketing people found the right leads?

Allison: Because product designed and scoped it the right way? Or because engineers built it the right way, right? Whereas in other segments and sections, it's a little bit easier to map.

Allison: And so there's a couple of things that come with that, right? One, there's always the question.

Allison: I think the question is even more today with AI of, like, what are my engineers good at coding, like, at the work they're doing? Can they be more productive?

Allison: Are they being as productive as they can possibly be? Like, essentially, like, what am I getting for all of this money that I'm spending? So that's one piece.

Allison: The other piece, I do a lot of, like, I would say crossover HR engineering work because engineering departments tend to need things like more robust levels and expectations so that people know.

Allison: The company and individuals, there's accountability, there's responsibility. Like, they tend to hit hiring issues, right? Because they're not looking for one of or a second or third person on a team.

Allison: They're looking for the 30th engineer that kind of needs to do this and kind of needs to do this. So they hit some, like, hiring pipelines.

Allison: So they hit a handful of, like, those, like, HR milestones earlier than most other departments.

Allison: And before an HR person is ready to put, like, a robust company policy in place.

Allison: But they want something built for engineers that achieves the goals of what engineers want, but that don't lock the entire company into something untenable for as they start rolling those things out for the rest of the company.

Allison: So there's, like, HR milestones, there's, like, what are we getting for our money so that we know when and how and if to grow.

Allison: And then there's often just some, like, communication gaps, right, within the leadership team, within whatever, where engineering kind of starts to work a little bit more in a silo.

Allison: And that can, again, that can happen at five engineers. That can happen, that can start happening at 20 engineers. Usually you're deep into it by the time you're, like, at 50 or 60 engineers.

Allison: But that is the other piece that usually it's, like, okay, and the rest of the leadership team doesn't feel like they're necessarily getting the information.

Allison: And usually I, not always, but usually I go into organizations that have a CTO or that have somebody who has been sort of playing that communication role.

Allison: But they just don't know exactly how to communicate in the right way to the rest of the leadership team.

Allison: And so for me, some of that is coming in and doing it, and some of that is, like, coaching that person on how I do it, why it lands, why it's affected, right?

Allison: Like, when you watch someone do something, it's easier for then you to be like, oh, okay, now I know. Got it. I'm going to try that next time.

Allison: So that's a bunch of sort of inflection points, but it all, it's like that bucket of things.

Jeremy: All those seem to be about these scaling problems that usually there are people that are going through it the first time, you've been through it five times, and they just need to see how it works or, yeah. Okay, that's cool. Yeah.

Jeremy: Can, one thing that's, you know, I was thinking about when I was looking at your work history, you know, I see the fractional label a lot for fractional CTO.

Jeremy: But what's the difference between what a fractional CTO would do and what a fractional VP of engineering would do?

Allison: Yeah, this is a great question. And I always debate it because I'm like, what, like, I'm a fractional, I'm a fractional everybody in engineering reports to me, right?

Allison: And whether that's, like, whether that's, like, the CTO, ahead of eng, a VPE title, like, I don't, personally, like, I don't care.

Allison: I want to get in there and do good work and solve problems and, like, make things happen, right? So it's the fractional, all the people report to me sort of thing.

Allison: But the distinction and the reason why I often will sort of talk about VP of engineering as opposed to CTO is that a lot of times these companies that I'm working with, they have a founding CTO or they, like, they have something at that.

Allison: And honestly, like, I am not interested at all in, like, ego jockeying or in, like, oh, how do we explain to the company that, like, we have a CTO, but then we're also bringing in a fractional CTO.

Allison: And so there's usually somebody in that seat and also that person really wants to stay deep in the code. They want to be doing the architecture review.

Allison: They want to be working with the principal engineers. They want to be thinking about, like, that, like, or they do a lot of speaking, right, that sort of thing.

Allison: And so that's often why I talk about fractional, so that companies don't, like, count themselves out because they already have a sitting CTO and they feel like it'd get, like, weird or awkward.

Allison: But basically it's, like, the fractional, like, all the people report to me.

Allison: And I usually focus on people and process with a very strong engineering background and component.

Allison: But usually my focus is not we need to rewrite our entire architecture and you're going to be the person that's, like, sitting in those meetings and doing those things.

Allison: I'm usually the person that makes sure, like, okay, what is the plan that you put in place? Let me ask questions. Let me double check that.

Allison: Let me, like, make sure that you're meeting milestones on the right path to putting that plan together, bringing in the right stakeholders, et cetera, et cetera.

Allison: So, yeah, that's kind of, in my mind, the difference between, like, VP of engineering, CTO, right, that sort of thing.

Jess: That makes sense. That makes sense, yeah.

Jeremy: Yeah. I, most of my, almost all my career has been in really small organizations.

Jeremy: So, uh, there's often not even a CTO or, or there may be one, but it's hard to say, like, is that really something when there's only two developers or, you know, that kind of thing. Uh, so that makes sense.

Jeremy: How often do you think is that CTO that you're working with? Are they, are they often getting ready to move into a VP of engineering role? Or is it rare that they kind of, like, make that jump?

Jeremy: Are they happy to say CTO level?

Allison: They usually like to say that, that CTO level.

Allison: They, they usually need help, again, with, like, people, process, but also somebody that, like, understands engineering and can, like, can speak engineer with, with them and understand, like, problems at, at that deeper level.

Allison: You know, most of my contracts end with them, with me basically saying, like, okay, it's time.

Allison: Like, let's, let's find you, like, an amazing full-time VP of engineering. Um, or sometimes it's, like, actually, like, we have a lot of this stuff worked out. Your team's doing well.

Allison: And what you need full-time is a really experienced senior engineering manager or director of engineering. Okay. So, yeah.

Allison: So you, or, like, I've been working with this person and I, I think that I should exit and you should promote this person to director of engineering or to VP of engineering.

Allison: And we can make it a really, like, a seamless transition that way. So, um, yeah.

Allison: But usually the CTO stays in that, usually they stay in that, in that seat.

Allison: So, and so I will say, like, the best CTOs, uh, the best engagements for me in that role are ones where, where the CTO is, like, pretty self-aware.

Allison: And they recognize, right? Like, sometimes, like, I get brought in, like, by the CEO or by, like, somebody else, you know, a chief of staff or whatever who's, like, we, we need someone.

Allison: And in that case, it's a little bit of, like, conversations with the CTO that's basically, like, like, I'm not here to, like, steal your thunder.

Allison: I'm not here, like, I'm here to work with you so that you can do an amazing job in your role. And I can cover, like, this, you know, this part and piece over here.

Allison: Um, but the best ones are the ones where there's, like, a CTO or a CEO, CTO team that say, like, okay, we, we're hitting these milestones. This is starting to feel painful.

Allison: We know that there's a gap here. We know that we don't have the depth of management. Or, like, I've seen this a dozen times before experience. Who, who can we bring in?

Allison: Who's, like, people first, business focused, et cetera, to cover that, to cover that gap and to make sure that we don't drop the ball or that our company fails, like, because of this reason.

Allison: Those are the best. Yeah,

Jess: that makes, it makes a lot of sense.

Jess: Because, at least in, in my circles, the CTOs that I know of are people that are either technical co-founders and they're developers that have just grown into that role.

Jess: Um, and they still enjoy developing and writing code and, you know, nerding out on all the, the technical parts.

Jess: But there is another part to that job of managing a team and leadership and people and that they're not always equipped to handle.

Allison: Yeah, and often I'll say, in those conversations, I'll say things, like, when I'm talking to a CTO or even when a CTO is, like, skeptical about bringing someone.

Allison: You know, I'll say, like, well, like, what are the, what are the things that are on your plate that you absolutely love, that you would be really sad if they came off your plate?

Allison: What are the things that are technically on your plate but you actually, like, never have time to do but that you want more time to?

Allison: And what are the things that you know you should be doing but that just, like, never actually get prioritized, like, never come high enough on your to-do list to actually get those done?

Allison: And part of that is how I scope my, my arrangements because, like, I don't want to, I don't want to come in and do something that the CTO is, like, no, I love that so much.

Allison: Or if it, like, makes sense for me to take it, then I'll talk to them and be, like, okay, well, look, how about we, how do you feel about this?

Allison: So you get to do this part and so you keep this portion that you love and I will do this portion, which is, like, the follow-up or the get things done or the change management that needs it, whatever that is.

Allison: So that's also a lot of how I, like, how I scope is, like, I don't, I don't want to, like, you don't want resentment. Again, it goes back to, like, do I care if I'm, like, the CTO, the head of ENG, the VP?

Allison: No, I'm the, like, fractional people report to me, right?

Allison: So same thing when I'm talking to a team or a CTO or a leadership, I get a sense of, like, what are the things that fill their cup and that they love doing and how can I scope my arrangement to enable them to do more, better, different, whatever of that while doing other stuff that is also important.

Jess: And I imagine there's a few, few items that are on the category of, I didn't even know I was supposed to be doing these things, right?

Allison: Yeah, yeah, yeah. Or just, like, can you take this so that I can see how to do it differently, right?

Allison: Like, it's one of the things that I talk about a lot in my workshops is, and at conferences, is, like, how to make your meetings suck less.

Allison: Because, like, again, it goes back to that, like, please stop wasting my time, and I do not want to waste anyone else's time.

Allison: And so sometimes it's, like, oh, we have a department meeting or we do this thing because it feels like we should do this thing and we need to do this thing. But, like, it's not great. Nobody really loves it, right?

Allison: And so in that case, it's sort of, like, okay, cool. Well, let me, like, organize and see, like, sort of put it together. You still have a critical role in this section or in this section or, you know, whatever.

Allison: But it's just a different way of thinking about doing these things. Same thing with off-sites when I work with engineering managers.

Allison: Like, they've always, like, when they do knowledge sharing, for example, right?

Allison: It's always, like, oh, we have a projector, somebody shares their screen, they walk through the code, they give people a chance to, like, ask questions. And, you know, it's, like, cool.

Allison: You could do a knowledge sharing section in a completely different way, right?

Allison: But it's just, if you haven't seen it, if you haven't seen that depth of, like, facilitation approaches, exercises, different things that you can do, like, that's often, you just, you don't know it exists if you haven't seen it before.

Jeremy: Yeah. That makes sense. And that's why, having worked at these, probably these other organizations that have already gone through those scaling changes or transitions or getting to see that, you can apply that to teams that just have never.

Jeremy: It's not like they're not smart enough, it's just they've never had the opportunity to see that before.

Allison: Exactly.

Jeremy: I'm curious what, all of this makes sense, like, in terms of what you're doing and in the transition from, like, full-time work into consulting.

Jeremy: But was there anything else that led you to pursue consulting as a way to do your work?

Allison: It's a good question. I mean, I had always, look, I had a startup, so I knew what it was sort of like to, like, be out of my, you know, and start, start.

Allison: And I've always been involved in different, right, like, Ruby Central, we, like, rotated who sort of, like, planned RubyConf and RailsConf, and that's why conferences sort of look different, like, one to the other, because whoever was responsible got to, you know, sort of, like, execute their vision of, like, what they thought the conference should be.

Allison: And so, you know, I had thought about going out on my own in the past, but I think going out on your own, and there's a lot of stuff about going out on your own that people don't talk about.

Allison: Like, I feel like right now it's, like, it's cool to, like, go out on your own and to, like, be fractional and, like, do, you know, like, do these things.

Allison: And that's great, and I do love, like, having my own business and doing consulting, and there's also a lot of stuff that's really hard about it.

Allison: And so, in the past, when I thought about it, I think about, like, okay, do you have the network, do you have the experience, and do you have, like, a set of skills, right?

Allison: Do you have the offerings, and I would say in the past, when I've thought about it, I didn't feel like I could check all three of those boxes. And then a couple of years ago, I mean, look, it was also, like, tech was changing.

Allison: There were tons of layoffs, right? The interview processes were, like, not great, right?

Allison: And so, when I thought about what I really wanted to do, I was, like, oh, I think I can check those boxes now, and I think that I can actually pull together really good offerings of things that I also love to do, and let me try it for six months and see.

Allison: And if it doesn't work, then I will, you know, look for a full-time job sort of thing.

Allison: So, but it was, I mean, like, when I first started, it was, you know, people were, like, oh, you must have, like, such, like, great work-life balance and so much flexibility.

Allison: And I was, like, no, it's, like, so much worse than when I had a full-time role. Like, when I was getting off the ground, and even sometimes now, it's, like, 60-hour weeks, you know, like, it's

Jeremy: not. It's hard mode.

Allison: Yeah, I mean, people are, like, oh, we're, like, how do you find your clients?

Allison: And it's, like, I freaking hustle, like, I hustle, and I, like, keep in touch with everyone, and I do a bunch of biz dev, and they don't just, like, I don't know, for some people, it feels like they fall into your lap.

Allison: But that feels, like, few and far between, right?

Jeremy: I think a lot of people ask that thinking there's a secret job board where you can find clients. It's, like, a job board. You know, like, because that's the big, that is the top question that people ask me.

Jeremy: Like, where do you find your clients?

Allison: Same, all the time.

Jeremy: And what you said about, like, those three things that you need to have, that's often, like, I'm cautioning people, like, you need to make sure that you are already good at the thing that you are providing services around. And then you need some other skills.

Jeremy: You need marketing. You need sales. You need to make sure that you're organized. You need to know how to do your finances. You need to be able to do all the job plus all the business stuff, and then you could be ready.

Jeremy: It's still going to be hard because you're going to do all those things.

Allison: And some of it is out of your control, right? Like, there's a very big, like, serendipitous piece to, like, I post on LinkedIn, right?

Allison: And people are like, oh, do you get clients from posting on LinkedIn? It's like, do I get clients from posting on LinkedIn? Not directly, right? It's not like somebody was like, I saw your LinkedIn post and decided to hire you because of that.

Allison: But what I need is everybody that I know on LinkedIn, when they're mindlessly scrolling through, that they see my name and they say, oh, I just had that conversation with so-and-so yesterday.

Allison: I should totally connect them with Allison, right? So it's like, it's just, it's staying top of mind.

Allison: And there's just a lot of things that you do to stay top of mind, to evolve what you offer, to, you know, sort of, like, be helpful and useful, like, person, just making connections in general between people.

Allison: And so, yeah, there's a lot that goes into it. And I'm like, you know, people will ask me about running my own business.

Allison: I'm like, you know, I have a boss and, like, sometimes she's the best boss and sometimes, but, like, most of the time she's, like, the worst boss and she's me.

Jeremy: Yeah, exactly. Yep.

Jess: What kind of engagements do yours usually look like? Like, can you, will you typically have, like, four or five clients at one time?

Jess: Or is it, like, very intense and it's one client at a time or maybe two?

Allison: Yeah. So my balance is, and it, this is where it depends because of the different kinds of contracts that I offer, which is actually how I, how I like it to be.

Allison: Like, I like that variety of, like, I'm going, I'm going deep in here. I'm a little bit, like, in and out here, you know.

Allison: So I would say I only do, like, a maximum of two fractional clients at a time because I, I really want to be able to ebb and flow with the team.

Allison: And if I have too many fractional clients, like, I just, I can't give those teams, like, what they need from, because I'm also, like, I scope my projects, but, like, if I'm in the seat, I'm in the seat, right?

Allison: And if something comes up, like, you know, I'm not going to be like, oh, sorry, your engineers were up for the third night in a row at three in the morning. Like, we're out of hours for the week. I can't do anything about that, right?

Jess: Too many fractional as a whole, right?

Allison: Yeah. So, so fractional, like, one or two clients at a, at a time. Again, depending on, like, the engineering size and sort of what's, what's going on in there.

Allison: For off-sites and workshops, I mean, in, like, the most ideal scenario, a company is contacting me 12 weeks before so that we can, like, have a really robust, that is, like, very ideal scenario.

Jeremy: Three, three, three months is ideal?

Allison: Three months is ideal, yeah.

Jeremy: I was thinking more, like, six months. I mean, like, so they must contact you, like, a month before? When is this, when is it often happening? So usually, so

Allison: I won't take stuff that, if they contact me, like, three weeks before, there's just not enough time for me to, like, really do a good job.

Jeremy: Good.

Allison: Except for, like, a couple of one-off workshops. I have a couple of workshops that I can, like, turn around pretty quickly.

Allison: But, yeah, usually it's sort of, like, six to eight weeks in advance when they're contacting me for off-sites.

Allison: So I can do, I would say, depending on, and then I have to be there in person to facilitate, so that depends a little bit on the calendar Jenga.

Allison: But I can do, you know, like, four to six workshops, trainings, off-sites clients. Again, depending on, is this a workshop for 100 people?

Allison: Is this a workshop for 20 people? You know, what are they looking for?

Allison: And then, you know, one-on-one advising and mentoring, that one is, like, I keep it as, like, a pretty light lift, so, you know, so I can take on a number of, like, a number of clients in that space at once.

Allison: So there's usually, like, a, there's usually, like, a mix. You know, the trickiest part is that week of, it's really hard to get on my calendar. So, like, week of, it's really hard.

Allison: So if somebody's, like, oh, I can't meet today, do you have time to reschedule to tomorrow instead? It's, like, I probably don't. One week out, it's a little bit easier.

Allison: And then two weeks out, it's usually, like, much, much clearer. So that's the only thing about that sort of number of, number of clients.

Jeremy: You have a really cool mix of things going on. That sounds, like, ideal to me. Like, that's part of why I like freelancing, consulting, is having a number of projects, being in a number of roles, and having different, like, sizes of things.

Jeremy: Just because, I don't know if I get, I mean, partly it's I get bored. Like, if I'm just doing, just in one area, like, I want multiple things. I just need multiple things going. I don't know why my brain is like that, but I kind of need it.

Jeremy: And it's maybe not what most people would like, but doing it this way, like, makes me feel alive in my work in a way that's really important to me.

Allison: Same. I enjoy the context switching. I enjoy, I mean, for me, it's also really cool.

Allison: Because I get to see, well, I'll say, like, with, I'm doing a lot of AI work from a few different directions.

Allison: Like, non-profits that, like, just want sort of a broad, like, how do we, we don't want to be left behind. How do we get more into AI? What does this look like?

Allison: You know, companies that are really sort of trying to, like, drive tech companies that are really driving AI adoption and trying to figure out, like, how to get people over, like, over certain humps. So, a variety of AI work.

Allison: And the cool thing about that is that I get to see a lot of these things from differently embedded fractional perspective, from the sort of, like, I'm doing a longer workshop.

Allison: Oh, I'm just, like, coming in and doing a shorter workshop and then checking in on them.

Allison: You know, doing a little bit of embedded AI engagements where they want trainings, but they also just want to be able to, like, me, like, read over their AI policy or, like, ask questions as they're actually trying to do things.

Allison: And they want those trainings to be not, like, one company training, but, like, can you do this slightly more specific training for this department?

Allison: Or we want to, you know, this training for this, that sort of stuff. So, I'm seeing, I'm doing a lot of AI work from a lot of different angles.

Allison: And the cool thing about that is that I'm also able to see it, like, how does, how is a nonprofit, how is a small nonprofit looking at this? How does that, how is a larger, well-funded nonprofit looking at this? How is a tech company looking at this?

Allison: How is an engineering team looking at this versus a marketing team looking at this? That's cool.

Allison: What are my, what are we hearing from VCs about, you know, what their expectations are of these different companies that they're funding? So, it's, it's really fun and really cool.

Allison: And I think pretty unique to be able to, like, see it from a bunch of different directions.

Jeremy: And for any of those clients, where else would they find someone that had been able to see it from that many angles? Like, they're probably not going to be able to find somebody that could do that. So, that's cool. Yeah,

Allison: exactly. Well, and that's, like, honestly, part of how I evolve my offerings is I talk to a lot of people, right?

Allison: Like, people that I'm keeping touch with, events that I go to, just, and I'm always trying to figure out, like, what is the thing that everybody's talking about, struggling with, asking for, right?

Allison: What is the topic that's coming up in every conversation? And in what way is it coming up in every conversation? And from, from there, because there's, there's a lot of things that I can facilitate.

Allison: There's a lot of things in this technical, non-technical space that I can do. But if you say you're everything, then you're actually nothing, right? If you're everything for everyone, then you're nothing for anyone.

Allison: And so, how to kind of, like, evolve those things based on what I'm hearing to have an offering that then I, like, start talking about in conversations or put on my website or start posting on LinkedIn.

Allison: And because you can tell, I think this is in the consulting world, and also this was the case in the startup world.

Allison: People really want their ideas and their things to work, even when they're not getting that feedback that they're really landing.

Allison: Or, like, the feedback that they're getting from people are, like, they're talking to people and saying, like, do you think this is a good idea? And they're saying, like, yeah, I think it's a great idea. Because nobody wants to say, like, actually, I have absolutely no use for that.

Allison: And, like, you're not qualified to do that. Or, like, I would never buy that. Or, right? People want to be nice to each other. They want to be encouraging each other. And so, instead of asking that, I just try to, like, pull on threads.

Allison: And then, when it feels like there's something, I'll be like, oh, I'm now offering blah, blah, blah. And if it sells, or if people start to be like, oh, send me more information on that.

Allison: Or, like, yeah, let's set up a follow-up call. That's when I'm like, okay, cool. This is an idea. But if I have an idea, and I say it in 10 conversations, and everybody's like, oh, yeah, that might be cool.

Allison: Then, like, it's not going anywhere. And I, like, drop it and move forward.

Jeremy: Yeah,

Allison: yeah,

Jeremy: exactly. I do the same thing. Yeah, conferences is, like, a great place to, like, I'll just, like, soft pitch, you know, or just, like, describe an idea I have.

Jeremy: And then I'm waiting to see, like, you know, the, oh, that's cool isn't enough. Like, that's not it. But if they ask more, or they're like, oh, like, see their eyes light up, and then they're, like, asking a bunch of questions. They're curious about it.

Jeremy: Then I'm like, okay, maybe there's something here. And it's, like, an easy way just to, like, soft test that. But social media, too, like, totally being able to do that. I think about it a lot of times, like, fishing.

Jeremy: Like, you're trying different bait, you know, throwing it in and trying to see if you get any kind of snags, any kind of bites. And it doesn't mean you're going to get a fish, but you're just trying to get some sense. And you just got to do it over and over again. Just try different things. Oh, I think this might work.

Jeremy: I think this might work. And, like, continue to show up that way over and over again. Yeah.

Allison: Well, and this is from my days of having a startup. I think one of the most important lessons that I learned.

Allison: I did, like, a lean startup weekend, which was really interesting.

Allison: But I think the main thing that I took away from that is at some point during that weekend, you actually go out onto the street and you try to talk to people.

Allison: And you try to get them to give you $1 for the thing that you, for the idea that you have. And it's amazing how many people are like, yeah, yeah, that sounds cool. Like, I totally buy that, blah, blah, blah.

Allison: And when you say, like, okay, great, it costs a dollar. Can I have that? Like, can I have that dollar now? So, and then, like, I'll send you something later. Like, it's amazing how many people are like, no. Right?

Allison: And so I think that that's also, right, when you try something or vet something through, like, a free workshop or a free whatever. People are like, oh, this idea is super successful.

Allison: I've offered it for free a bunch of times. And, like, and people have shown up. That's great and that's cool. And sometimes I'll, like, do some things for, you know, for free.

Allison: But the question is, like, will anyone, because it could be a great idea. But, like, if it's a great idea that people don't feel like it's worth paying for or they're not actually walking, like, that's also a thing. Right?

Allison: And as a consultant, you have to figure out. And honestly, as, like, an engineering tech consultant, like, we are expensive. We are more expensive than many other consultants out there.

Allison: And so the other piece is, like, not only will someone pay you for this, but will somebody pay you a rate that feels like it makes sense for the thing that you're offering?

Jeremy: Yeah.

Allison: Which is hard, right? There's a lot of, like, economics and, you know, or people say, like, oh, I did this for free and it didn't. It was fine because it was just one hour and it didn't cost me any money.

Allison: And it's like, okay, but did you email people about it? Did you post on social media? Like, it's not just the time for that thing that you did. It's, like, all the other time that you put into, like, the promotion, the planning, the blah, blah, blah.

Allison: What was your actual all-in cost for offering that? And how much did you land collect? Like, how much did you then get out of it as well?

Jeremy: Now I've got to ask, I'm a huge time tracker. Do you track your time when you're doing all of that to figure out what your fully loaded costs are for those kind of things? I

Allison: do not track my time. I am an anti-time tracker. I hate, actually, if somebody's, like, somebody's, like, yeah, I'm interested in this, but can we do it, like, hourly or can we time track? I'm, like, no.

Allison: Do we have to? Like, tell me your reasoning for, like, wanting to specifically, like, time track the, like, the exact hours or whatever. No, I'm not a time tracker.

Allison: But I am, like, a, I do, like, reflection.

Allison: And when I look back at my week, I will sometimes sort of be, I will sometimes say, like, okay, of all the meetings that I had this week, like, how much was client work? How much was biz dev?

Allison: Like, how, what categories do I put it in? And how do I think about those categories and sort of, like, the overall cost of my week?

Jeremy: Yeah, actually, that's, I'm curious about this for you, because I have been telling people that if they want to work for themselves, like, at least doing kind of the way I do it, like, fractional, I'm just, like, I call myself, like, a fractional product, you know, developer, as a Rails developer, that they should still count on around a quarter of their time with marketing and biz dev.

Jeremy: Like, in previous times, I didn't do that, and I skated by, but then my network was really thin.

Jeremy: And so then you're really making it dangerous for you when one contract winds down, you've got no leads at all, and no one knows your name. No one knows that you offer services.

Jeremy: So now I, and I, for me, I broadly count that as things like putting on a conference talk, putting on a conference, you know, doing the podcast, other things like that.

Jeremy: I'm curious if that ratio sounds right to you, or if, like, if you have something similar, or what yours is, like, how do you think about that?

Allison: Yeah, yeah, and I think that it is very similar. It also depends on, like, if I have a super full, if I have a super full client load, and I know that I'm probably not going to be able to take on anyone.

Allison: Now, I always keep some of a pipeline, right, because clients disappear quickly or stop, but, like, there's always stuff that happens.

Allison: So I don't completely forget about that business development, but, you know, when I'm, like, looking at the market, and a lot of other people are struggling, right, I'll ramp up that, that biz dev time a little bit, or ramp it down if it feels like I've had a lot of, like, inbound, or there's something, you know, there's a lot of stuff that's, that's coming.

Allison: I will say I also, I have an assistant, I have a virtual assistant who is really, really, I mean, she does both professional and personal stuff for me.

Allison: So there's a lot of, like, mom tasks that just, like, take up a lot of time that I, like, like, hey, we got an email from, like, the soccer team, and she makes sure that, like, all those games are in the calendar with the location and the time, and if travel time is needed, that that's also blocked and, like, on the right calendar, you know, whatever, all of those, like, parent things.

Jeremy: Interacting with schools is, like, it's the freaking hardest thing. Holy cow.

Allison: Yeah, yeah, so she does personal and professional. That's cool.

Allison: But she also, like, helps with a lot of my, like, either keeping on, keeping me on track of schedules and, like, things that we've set in, in the past, or, like, for example, a lot of my social media, I'll sort of, like, I'll try to take, like, two hours in an afternoon, and I'll try to get all my posts, like, ready for the, for the month.

Allison: And then she's the one that actually, like, posts them to make sure that they're posted, like, at the same time, or that people are tagged in that, whatever it is.

Allison: So, yes, so I, I also have an assistant who's, like, very, very, very helpful in all of that.

Jeremy: That's cool. That makes sense.

Jess: I think I read somewhere that it, it took you four tries to get this person.

Allison: It did. It did, yes.

Allison: And this was, so, talking about consulting, like, this is something interesting that I do, I don't know how much other people do it, but I have these, like, side quest offerings, too.

Allison: Basically, when there's something that, again, like, I've been asked about so many times that I am just sort of, like, I should just put this out there in the world.

Allison: It doesn't neatly fit under the umbrella of, like, when I say sort of what I, what I do.

Jeremy: Yeah.

Allison: Yes. So, my virtual assistant, so I had, this is my fifth one.

Allison: I went through four before I found, and it was a learning process for me of, like, I had a decent system set up, but for me, the learning process was, like, I gave people a lot of, right, as somebody who, like, does management and communicate, like, I gave people, like, a lot of feedback, and I gave them, like, a lot of great, right?

Allison: There were some people that I just didn't say early enough, like, this isn't working, I need to find someone, someone else, really understanding, like, how do I describe what I need in a person for the tasks that I, like, that I need them for, and understanding, like, what I need.

Allison: Because, and for a lot, I was like, well, I'm kind of a lot, so, like, it's probably me, like, I'm probably the problem, as opposed

Jess: to, right? Well, you don't know how to measure that learning curve.

Allison: Yeah, right, I was like, maybe I'm, like, not describing stuff in the right way, maybe I'm not, like, maybe I'm not communicating effectively, like, I tend to look at, like, myself before I sort of, like, look at, you know, and so I ended up putting together this, like, this training course that has, like, a PDF for each episode, and a Notion template that you can just sort of copy in.

Allison: That's just as, like, if you feel like you need a virtual assistant, but you're trying to figure out how to not go through four before you get to one that, like, really works, and how to set up your systems, and how to blah, blah, blah, that it's, like, out there, out there in the world.

Allison: That's cool.

Allison: But, yeah, it was really understanding, like, what are the tasks that I really need this person for, and, like, what do I need in terms of, like, independence, working through ambiguity, communication style, all of those things.

Allison: And kind of being, like, really, I mean, I work through an agency, but kind of being pretty strict on it, with, like, these are the things that I need, and if you can't provide that, that's fine, but, like, you know, and I obviously want to give this person a couple of weeks, but after, like, two weeks, if it doesn't feel like it's working, then, like, I don't want to continue to give feedback and train, and et cetera, et cetera, et cetera.

Allison: Interesting. So, yeah, it was a journey, but my virtual assistant is amazing.

Jeremy: That's cool. I might need to consider that at some point.

Allison: Yeah.

Jeremy: Have you, oh, sorry, go ahead.

Jess: I was just going to echo that at one of my companies, we had a VA for a little while, but that didn't quite work out, and then we went, we wanted somebody to help with support, and it took us about three or four times to get the right person.

Jeremy: Yeah. I've been trying to decide if I want to try, like, doing, like, people do, like, AI chief of staff or AI operation agent thing.

Jeremy: I haven't tried this yet, but I've been thinking in the past few weeks, like, maybe I should give this a shot and see if it could, like, I'm pretty good on details, but there's just a lot of different things going on.

Jeremy: And you don't, you don't, you don't know what you might be dropping or the opportunities that you're like leaving on the table because you didn't have the brain space to really process certain things.

Jeremy: Or, um, I usually don't forget things very much, but there's always ways of connecting one work, you know, client, one set of work that I'm doing for one client.

Jeremy: And there might be tie-ins to what I might do for other clients or even things that could turn into talks.

Jeremy: Like, there are a lot of times when I'm working, I'm like, oh, that would be, this would be a, for a course I'm thinking about making, but I, like, it just, like, floats through my mind and never makes it anywhere. So there's all those kind of things. I'm like, I wonder if doing that would help.

Jeremy: Have you tried anything like that yet?

Allison: You know, I, I haven't, and I know there's, like, yes, a whole, like, AI, like, orchestration.

Jeremy: Yeah.

Allison: Um, I haven't done anything. Now, I and my assistant both, like, use AI a lot for a lot of different things. And there's, there's more stuff that I'm considering.

Allison: Like, I will say personally, like, I don't have, uh, I mostly use Claude. I don't have it, like, hooked into my email yet because I feel like I get a lot of things in my email.

Allison: But my assistant does, right, but my assistant does, like, email triage. So she'll, like, look at my email and tell me, like, she'll respond to some things. And then she'll, like, tell me, like, hey, these things, like, need, need a response.

Allison: Um, there is, like, one email address that I'm sort of, like, well, maybe I could hook AI into that and just have it run, like, a what's in this inbox right now.

Allison: And then she would, but then, I mean, she would still look over it and be, like, okay, cool, so these things can be deleted or let me, as a human being, sort of, like, click into that email and, and respond or read or whatever.

Allison: So I'm, I'm thinking about it in that way. I found that, um, what have I found?

Allison: Uh, I found that people that have the whole AI agent orchestration or, I don't want to make too big of a generalization or assumption, the people that I've talked to that have very robust, like, agent or agentic orchestration, um, are the people that really kind of, like, do very much the same thing every day.

Allison: So every day they're, like, doing a blog post and every time they do a blog post, it has to, like, have X, Y, and Z happen to it and it has to be sent to, like, A, B, and C places, right?

Allison: I think it's, like, why it works well for software developers because it's, like, every time that I push code, like, this needs a pull request description.

Allison: It needs instructions on how to test, it needs to, like, run these guardrails, it needs to be checked for X, Y, and Z, um, before any human, like, even touches a review of a pull request.

Allison: And so I think when you're doing a lot of similar stuff every day, then, like, that orchestration, like, makes a lot of sense if you're not, and I, I had a conversation with Claude about this because I said in, like, in a chat, I was, like, everyone's using skills or everybody's using, like, these, like, this, like, robust, agentic orchestration.

Allison: I'm not, I feel like I'm missing out, like, tell me, like, from what you know of the work that I do, my business, blah, blah, blah, like, what should I be using skill, like, what should I be using these different things for?

Allison: And we went back and forth a little bit and it was, it was basically, like, yeah, there's nothing that I do, that I do exactly the same way so many times in a row that it necessarily makes sense to, like, dive deep into that, into that orchestration.

Allison: The last thing that I'll say is that also, I think in order to get the most productive things or the most out of, like, agentic orchestration like that, you really have to make some decisions about security and access.

Jeremy: Yeah.

Allison: And those are trade-offs that, like, I am not quite there yet on.

Jeremy: I feel that. Yeah. It does worry me.

Jess: I was going to, I heard a good tip from Joel at Rails World and his talk and he was, he has a review skill that he runs after every, I guess, like, PR or maybe conversation.

Jeremy: Session for, yeah.

Jess: And it's, the purpose of the skill was to identify anything that could be improved and I think that means, like, could, could we, you know, make this repetitive?

Jess: Is this something that we could, like, write an SOP for or extract out and, you know, do easy, make it easier next time?

Jeremy: I like that.

Jess: That was my takeaway anyway.

Jeremy: I probably should be doing more of that just in general. It's one of those things that, like, there's so many things you could do working for yourself. There's, like, that bottom tier of things that you just never get to. It feels like that.

Jeremy: That's the kind of thing that would, but it would be the kind of thing that, like, makes you better, just, like, makes you more efficient or helps you, you know, improve quality of life in your business. All of that stuff.

Allison: Yeah. Yeah. I mean, one example that I have is, right now I have my assistant, like, every once in a while she'll, like, go through, like, conferences that I want to speak to.

Allison: Or that I just book it just to sort of check, like, is there a CFP open? And I've been experimenting with basically a scheduled task that once a week, like, I've given it the websites for those conferences.

Allison: And once a week it goes through and it says, like, is there a call for speakers, like, open or not? And, you know, when's the day? And so that's an example of something that's, like, I have a person doing right now.

Allison: I can probably automate, like, I've been running it for a few weeks to see how, like, correct and robust it is. And, you know, that's the kind of thing where it's, like, cool, we can probably just, like, run that.

Allison: Which, again, saves time for her to do. Basically, I have an endless to-do list of things for me or her. Or, you know, sometimes I say to them, oh, my kids are bored, I'm like, you want me to give you a task?

Allison: You want me to do some work? I always have an endless to-do list. And, you know, whether it's, like, household or work or whatever. No doubt.

Allison: And so I always feel like anything that I can give to AI, you know, it just makes space for more, better, different things that I, my assistant, you know, someone else can do.

Jess: That's cool.

Jess: I think another side effect of this is that it's not necessarily that the AI is doing the job for you, but it helps you to identify a checklist or a process for doing that job.

Jess: And maybe it speeds it up a little bit, but it helps, you know, any business, like, good businesses are systems of processes. They're SOPs, they're checklists.

Jess: And the more you can get something into that, then the better it is.

Allison: Yeah.

Jeremy: Allison, when I see your posts on LinkedIn and various other places, I'm often seeing these interesting events or unique services that you offer, like, recently, like, speed mentoring.

Jeremy: Fractional Women's Summit, AI Day of Learning, the Patagonia Walk Shop. And this one in particular is, like, I don't know if I need to go to this, but I feel like I need to go to this. Like, I wish I had a reason to go to this. Sounds

Jess: amazing. I was looking for a way to sign up, but it looks like it's sold out.

Jeremy: Oh, dang, yeah. You design all these unique events.

Jeremy: Like, I'm curious, like, how you do that, like, how you figure out what those look like. And I got to know about this Patagonia Walk Shop. It sounds amazing.

Allison: Yeah. Yeah. Well, and I will say I can't take credit for a lot.

Allison: A lot of it is our people who have an idea or are doing something and they want to make sure that how it's structured and how it works is really valuable and engaging and interesting.

Allison: So, like, for example, the Fractional Women's Summit was brought on by a woman who runs a fractional women's community and wanted to do their first ever summit, but wanted to do it differently.

Allison: Like, there are so many ways in which conferences just totally miss the mark on actually, like, helping people engage and learn from each other.

Allison: So, for that, we want to have, like, sessions, but also really easy ways for people to get to know each other, for people to really connect beyond that, like, beyond that surface level.

Allison: And so, for the Fractional Women's Summit, that was, you know, a core piece of what I was brought in to do is look at the engagement and the experience of the day. So, beyond the schedule, beyond those sort of core points, what that looks like.

Allison: The Walk Shop is super cool and actually, this guy, Mark Rickmeyer from TXI, he's been running Walk Shop, I think, for, like, a decade. Wow.

Allison: And basically, once a year, it is a leadership hiking retreat.

Allison: So, it's about a dozen folks at different places in the world where there is a theme for the week.

Allison: But basically, you hike all day and you sort of talk about that theme and the place relates to the theme that's happening.

Allison: And then at night, you're, like, you're in a hotel, you're sleeping in a bed, you're not, you know, outdoors the whole time.

Allison: But, yes, but, you know, then it's, and it's a really great way to get to know, get to know people really deeply.

Allison: Our theme for Patagonia is the power of moments, the book, The Power of Moments, and sort of looking at these moments that we have on our leadership journey and what has had really big impact on us.

Allison: But then also, as leaders, how do we look at moments? How do we create those moments for other people? What does that mean? What does that mean now? What does that mean five years from now? Sort of that, that arc.

Allison: Yeah, so Patagonia is sold out. I'm very excited to be facilitating that one. Sounds awesome. It's going to be amazing.

Allison: But I know that Sweden, then they usually sell out about a year in advance. I mean, we posted this one, I think, like, eight or nine months in advance. Okay.

Allison: So the next one was just posted for Lapland, Sweden, and Northern Lights.

Jeremy: Yeah.

Allison: So, and you can always, if you go to Walk Shop, you can get on their sort of list for, like, tell me about these in the future. But, yes, I'm very excited.

Allison: I haven't been on a Walk Shop before, but everybody, like, says they're amazing. And so, yeah, a really, really cool experience to be able to facilitate and figure out, like, okay, what's the leadership arc? What do we want people to go through?

Allison: We want them to be discussing what feels meaningful and impactful, you know, while they're going through this very intense hiking experience as well.

Jess: Jeremy, I see a future for Ruby on Trails.

Jeremy: I know, right? I don't know if you know this, Allison, but, yeah, I do Ruby on Trails, like a backpacking trip for Rubyists on the Appalachian Trail.

Jeremy: And, yeah, so that, like, thinking about that, thinking about Blue Ridge, when I started Blue Ridge Ruby in 2023, I didn't realize, it, like, unlocked this thing in my brain where I realized, oh, I really like designing experiences for people.

Jeremy: And now I'm like, now that I go to a lot of conferences, I see all kinds of things that I either don't like, you know, I can appreciate any conference, you know, every conference I enjoy, at least to some degree.

Jeremy: But there's always things like, oh, that could have been, that could, they really could have helped people connect at the beginning, right after registration, and they didn't, you know, things like that.

Jeremy: Or there are times where the conversations are just really good, and I think it has to do with the context and the environment that was created, not necessarily just luck, you know?

Jeremy: And sometimes there's luck components about it, too, but sometimes it's designed, whether arbitrarily or not, or intentionally, like, it's designed for that. And I love that aspect of it.

Allison: The best conferences design it intentionally, but in a way that makes it feel serendipitous.

Allison: So this is like, sometimes somebody, it's happened once or twice in the past, where they're like, oh, we'd like you to, like, design this conference, and then, you know, but do it for free, and then it's like, you know, promotion for your name, and blah, blah, blah.

Allison: And I'm like, okay, but the thing is, actually, that if an experience, an off-site, it's a little different with a workshop, because you're, like, teaching content, but, like, an off-site or a conference, honestly, like, if it is designed well, you don't even recognize how it was, like, you don't recognize how much intentionality was put into that design.

Allison: So people don't really think to, like, call you later, necessarily, because it doesn't seem, because it seems effortless,

Jeremy: right?

Allison: It seems like serendipity, it seems like luck, and the best conferences, and really the people that organize these things know that, like, that there is actually a lot of work and careful planning that goes into making something seem effortless and lucky and serendipitous.

Jeremy: Yeah.

Jeremy: When you're thinking about whether designing, like, an online summit or off-site or doing things in person, what are the things that are key for you in helping people either connect or sometimes, I know it seems like you're designing events either for helping people connect or helping people through change.

Jeremy: It seems like those are two big things. I'm curious how you think about both of those when you're designing either offline or online.

Allison: Yeah. I think offline, online, however I'm designing, it is how people are connecting with one another and how people feel seen and heard.

Allison: And I think that's really, and there's so many different ways to do it where you can do, like, an unconference, or you can do something that's more asynchronous, or you can...

Allison: I mean, at the Fractional Women's Summit, we had three spots for stickers on people's badges, and I bought really cute stickers.

Allison: And one spot was, like, stickers of, like, things that are your hobbies. One spot was sticker of how long you've been fractional for, like, are you fractional curious, or, you know, so you can get a sense.

Allison: And the last sticker was, what is the primary thing that you're looking to get out of the day? And we had a key of, like, four different goals that we felt most of the people coming to the summit had.

Allison: And, you know, and I encouraged people. I was like, look at people's name tags. Like, oh, you do yoga. I also love yoga. Or, oh, you like martinis, or listening to music, or whatever it is.

Allison: But I had a whole bunch of different, like, hobbies on there. And so it's all about these micro-opportunities for connecting.

Allison: And I think that even when you're also doing, like, change management, it's also, it's post-its on the wall. It's like, what, you know, what are we fearful of? What's the worst that can happen?

Allison: And it's not just having those in large group discussions, where the loudest voice, or where it's, like, harder to moderate.

Allison: But it's really sort of, like, that progression of, is it individual, in a pair, in small groups, small groups that rotate, post-its, right? Kind of what that looks like.

Allison: So I think, but it's all about helping people feel seen and heard, making it easy for them to do so, and making it really easy for them to connect with others.

Allison: Like, everybody says the hallway track is, like, the best part of any, or, like, who you meet is the best part of any conference. Or at a team off-site, like, getting to know your team members better is the best part of any off-site.

Allison: But you kind of have to, we all rely on, like, that, those introverts to be, like, okay, are they, like, or if you are an introvert, right, that's how, and it shouldn't, it shouldn't and can't be that way, right?

Allison: You have to, like, create these opportunities that allows everyone to get something out of it and to engage, regardless of your style and personality and what connection looks like for you.

Allison: And, again, going beyond, like, where do you live? What's the weather there? What are your kids up to? You know, like, those sort of, like, surface-level conversations.

Jeremy: I really like the first two examples that you gave about the stickers on the badge and then post-its on the wall.

Jeremy: In both scenarios, it's giving people a structure to communicate without having to say things, which helps the introverts and the quieter people in groups.

Jeremy: Because people often are looking for icebreakers where you need to go find three other people and talk to them. You know, there's that thing.

Jeremy: Or it's, let's go around the circle and everyone say, share their piece, you know, share whatever.

Jeremy: And those are some structures for that, but it also requires everyone to assert themselves, to immediately be able to be on the spot and say the thing that's being expected of them.

Jeremy: Many people aren't ready to say that. It's much easier to communicate non-verbally if you give structure for that.

Allison: And if you have a large group, those are, like, so painful. Like, unless you are specific. Like, sometimes I will do, like, I want your name and finish this sentence in, like, no run-ons, no extra blah, blah, blah.

Allison: And you really, like, you got to moderate it, like, really, really well. Otherwise, those are also, like, oh, my God, we've now spent 35 minutes going through this circle. And I, like, don't remember anything about the first 10 people.

Allison: And also, I kind of want to die.

Jeremy: Yeah. Yeah. Yeah, people do that so often, thinking it's the way, it's almost like this formula. And as long as you do the thing where everyone gets to say something, then we're all going to feel connected.

Jeremy: And oftentimes, you're like, oh, my gosh, this is, that was so painful.

Allison: Yes. Well, and I think it's also, like, you don't, again, maybe a spicy, but, like, you actually don't have to be connected to everyone.

Allison: Like, if you walk away with, like, eight really good connections, as opposed to 40 super loose connections, like, I actually think it's way more valuable.

Allison: So you can do the around the circle, but, like, in smaller groups or groups that switch it up or, like, in a whole bunch of, like, variety of ways.

Allison: Because I actually think that like smaller things that can, that make stronger bonds is better than a much larger, much weaker bond experience.

Jeremy: One thing that

Jess: a lot of pressure on myself at conferences and I was like, I got to meet everybody and I got to, I got to figure out what, you know, just, it just, just so much pressure. And I agree.

Jess: Like if meeting just a handful of people is like more than enough and you shouldn't put pressure on yourself to, to do too much.

Jeremy: It does bring up something for me though, that I've felt in the past and I've also like, I wonder about, and that is like conferences are, can be expensive for people, you know, that may be putting two or three grand down to fly somewhere, stay, you know, hotel, pay ticket price.

Jeremy: And years back that always, you know, seemed really expensive. What am I going to get out of this? What am I going to learn? That's going to make this worth it. Who am I going to connect to? And you don't know.

Jeremy: And I wonder how, you know, when you, like if connections end up to me, they are the reason, like I care about those things now and I don't think about the cost as much, but I wonder like when you're selling either these kinds of services and it comes down to connections and they're like, okay, but we're talking about, here's the ticket price for connections.

Jeremy: You know what I'm saying? Um, it can feel, I think difficult for people to, to realize the value of that or to, uh, adjust themselves to that. Uh, especially if they haven't experienced it before.

Allison: Yeah.

Jeremy: Um, in a serious way.

Allison: Yeah. And I, look, I sell much fewer like conference experience, like the, you know, the walk shops are 10 people, the fractional women's summit, we capped it at a hundred, right?

Allison: Like for these larger conferences, because honestly, a lot of what it comes down to is, um, for attendees that are buying tickets, they often have to sell to their job, what they're going to get out of it.

Allison: And what they sell are the education sessions. And so conferences really want to pack as many like shins in there as possible.

Allison: So that's one to the other place that conferences get a lot of money are their sponsors and nothing about this, like really maps super, super specifically back to like back to sponsors and how sponsors are getting more like bang for their, for their buck in these sorts of things.

Allison: Yeah. So yeah. So that, that can be challenging. I think also, um, I don't know.

Allison: I don't want this to sound like judgy, but like there, there are a lot of people that it is hard to make the magic of connections and it's hard to quantify that. Yeah.

Allison: And there are, um, a lot of consultants that like are event planners and they're really good at logistics, but they're not really.

Allison: And so they'll promise that people can like make connections, but that's actually not like the thing that they're focused on or they're, they're like bread and butter.

Allison: And so I think that also, and this is actually like, I think every consultant has this experience where they're talking to a client who has had not just an event plan, but in everything where they have had a bad experience with a different consultant.

Allison: And therefore, or they really haven't like, I have, I run into this all the time with selling my engineering offsite work.

Allison: They actually haven't experienced a good facilitator that clicks really effectively with engineers. And so there's not high trust that I can be that person. Right.

Allison: Cause they've seen it. Like they've gone to the company thing. They've gone to blah, blah, blah. And they're, and they're always like, they've been like, I've just like sat in the corner, uncomfortable, praying that I don't get called on. Hold on.

Allison: And I can only say so many times, like I totally understand. And that's not who and what I am. Um, right.

Allison: And so same thing, like organizing when you're sort of guaranteeing like connections or guaranteeing this experience or those sorts of things, like people watch it be promised and not actually happen a lot of different times and in a lot of different ways.

Allison: And as consultants, it's, that's always the hardest thing to fight against is like, I know you've been burned in the past. I, I, I promise I won't burn you. I won't burn you. But like, what does that, what does that mean? Right. It's just, they have to trust you.

Allison: They have to like see it. They have to, you know, and as you do more, like obviously I have people that they can talk to, but that also only gives so much.

Jeremy: Yeah. They're still, yeah. They're still, even with, yeah. Even with, uh, reputation and reports from other people, there's still high trust in those situations.

Allison: Yeah. Cause, and they're expensive. Like that's like for me to, to facilitate, to put together a conference facilitated experience that really connects and brings people together for a thousand people.

Allison: That's, it's not a cheap, it's not a cheap offering.

Allison: Um, and it, again, like it shouldn't be a cheap offering cause there's a lot of effort that goes into making it seem serendipitous and seamless and amazing.

Jeremy: Yeah, definitely. I definitely think that there's so many, uh, future kinds of events that I want to do that I'm curious about. Like I've been big on the fractional thing for a long time. So I'm curious about that.

Jeremy: I told Jess, we should do an indie Rails offsite at some point, like, and bring together like other, either, you know, small SaaS owners or consultants and like just get away and get a house together, you know, for a weekend.

Jeremy: Um, I feel like now I need to do a Walk Shop or something. Like I need to find a way to do that at some, someday I would love to get a bunch of Rubyists on over the summer and like get a house for like a month.

Jeremy: And we'll all just like, uh, do a workation together.

Jeremy: Um, so so many things like this that I just like, you know, like doing a conference kind of unlocked, like, oh man, I just like, there's so many kinds of experiences that you could create for people.

Jeremy: It's just like super fun when, like when you pull it off, you know, and people have that, you like kind of step back and you see everyone doing the thing. And you know, like if you hadn't put on all that effort, it wouldn't have happened.

Jeremy: Those people would never have connected or whatever. And, uh, it just feels so good.

Allison: Well, and it really, I mean, I will say like right now it's, it's like a little bit of a, of a double-edged sword.

Allison: Like I have on my website, um, you know, a retreat that I want to do in the future for sort of like a, like a women in leadership treat that it's very, but that's very like no fluff, no be it.

Allison: Like it's like, what do we want to learn from each other? What do we want to know? Where are we at in our career? Like, what is the next step?

Allison: Like, it's very sort of like, and it's a little hard to show like what a sample agenda is because it's like, well, the people that are in the room are going to inform what the, what the agenda is.

Allison: But it, I think the thing that's interesting is that, um, it's a little bit of a double-edged sword.

Allison: Like, I think that retreats are like having a moment right now where there are, there are so many that are being offered and it makes sense because there's also this like, like massive loneliness epidemic, which is only going to get worse with AI and everybody using AI more and more.

Allison: And so people are really looking to connect and looking for those in person, those well run, like, you know, mindful, thoughtful, um, in person experiences.

Allison: And also there are so many coming onto the market right now that that like signal to noise is like really, really tough.

Jeremy: Yeah. It makes sense.

Jess: Do we have time for another question?

Jeremy: Yeah.

Jess: Or did you, did you have a burning one, Jeremy?

Jeremy: No, go ahead.

Jess: Um, I wanted to know about the, the Sliding Doors term. Is that something from the book or is that something from, from your consulting practice?

Allison: No, Sliding Doors is, it's actually a movie. I'm going to age myself. I don't know when the movie was.

Jeremy: Is that with Gwyneth? Gwyneth Paltrow? Yeah. Yeah.

Allison: Really long time ago. That's funny. Um, yeah, it's a movie where, oh my gosh, let's see if I can remember where like she, I think she makes a train versus she misses a train.

Allison: And basically your whole like life ends, like goes into like a different path.

Allison: Um, and so, yes, it, it is a reference to a, to a movie that is absolutely aging myself right now. It's basically this, yeah.

Allison: Sliding doors is it's, that's the name of the movie where it's basically like this really small thing happened. And then the whole movie is about basically like life in one way versus like life in a, in a different way.

Jeremy: Yeah. Huh. I can think of the cover of that.

Jess: You guys talk about on the, the walking.

Allison: Um, yeah, it's something that we, we are going to talk about on the, on the, cause it's a different theme every time.

Allison: So this one, and you know, and I describe it as like, for those who have seen the Sliding Doors movie, it's a really like people have that thought and that reference in their mind.

Allison: If they haven't, it can also be like a fork in the road or like a decision that you like decision large or small that you made that you feel like pushed your, your life, your leadership journey or whatever.

Allison: on sort of one direction versus a different one.

Jess: Got it.

Jeremy: I think, uh, for me, one big one for like a pivotal moment for me was going to Sin City Ruby after COVID and it had just come back.

Jeremy: And I think people were just starting to decide like, ah, should I go to conferences now? And it was in Las Vegas. There were 45 people there. I met almost everyone. Jason had designed it. So there would be 30 minute talks, 30 minute breaks.

Jeremy: So I got to, I got to have good conversations with almost everyone there. And it was a bunch of people that would, it was really helpful for me to have met.

Jeremy: And that was a major shift in my involvement in the Ruby community, my inspiration to like, want to do conferences to later than a year or two later put on Blue Ridge Ruby.

Jeremy: It was like a major, like, you know, Sliding Doors moment, I guess for myself. Um, which is really cool. I, and that's like the kind of thing I want to do for other people. Cause that's just like, so wonderful.

Jeremy: Like to have that, create that opportunity. Like people, it's not a thing that everyone's expecting or it's like, um, like this, like some kind of known, what am I trying to say?

Allison: It's no, there's no known outcome, but when you get the right people in the right room doing the right thing, like magical stuff happens.

Jeremy: Yeah. Yeah. And you can't anticipate all the things that'll happen, but you know, something good is going to come out of that. That will change some people. It'll like, it'll, uh, it'll inspire some things in the future.

Jeremy: And, and, uh, then those people will have that experience that they can look back on, which is really rewarding.

Allison: Yeah.

Jeremy: Do you have any sense of, I'm kind of thinking about the future, um, as we sort of get ready to wrap up, do you have any sense of what organizations are going to be looking to you for in the near future?

Jeremy: Like, I know a lot of it right now is like the, you know, how, how do we adopt AI and that sort of thing? I wonder if you have any guesses as to where your services might be in a year.

Jeremy: And I maybe don't, maybe not, it's not clear, but I'm curious. You seem to be very aware of the conversations that are happening and then adapting to those, you know, what your services to those curious what your thoughts are there.

Allison: Yeah, I mean, I think, and this is not, it's not one that I'm hearing a lot, a lot right now, but it is one that I am seeing.

Allison: I think that as, as companies adopt more AI and as teams get smaller because they're sort of like utilizing AI more, um, I think conversations are primarily going to be happening with AI as opposed to like across, like within teams or, or across teams.

Allison: And so I think there's, there's two things that things that are going to happen there. One, I think that, you know, engineers aren't known for their like super, super strong communication skills, right?

Allison: It's something that we're always like working on and looking at and looking at like, how do you give feedback? How do you engage in different ways, et cetera?

Allison: I think that with all of us sort of talking to our AIs in our own voice style and tone, um, I think that actually very quickly that team communication is, is going to erode or going to continue to, to erode because we're not, we're only practicing those communication skills with something that's trained to communicate with us effectively.

Allison: Like with a machine that's trained to communicate with us effectively, right? Um, so I think that team communication, uh, and camaraderie is going to come up.

Allison: So like, for example, it's, it's interesting cause I think more team offsites are back now for a long time. They were cut. I think they're back now.

Allison: Um, they often don't have like a facilitator or somebody that's sort of meaningfully designing them. Now the leadership ones do, right?

Allison: Like leadership offsites were never cut and often have a facilitator because they're like, oh, it's, it's worth it.

Allison: And I always try to push companies like, okay, but imagine if every team, like you feel like you get so much because the leadership team is like ready to do this offsite and you have someone designing and facilitating it mindfully.

Allison: What if literally every, uh, every one of your teams also had that and could get that much more out of that time together.

Allison: But I think that, so I think that in terms of offsites, I think just in general, in terms of like workshops or that time together, like that team communication and camaraderie, I think it's really going to go down and they're going to need companies and organizations.

Allison: We're going to need help bring it back up and that like chill happy hour or that like lunch together or whatever, like isn't, isn't going to cut it enough in the future.

Allison: The other thing that I, that I think is going to happen is like, especially for software engineers, but everyone in general, the way that they do their work is, is going to look different, is starting to look different.

Allison: In some ways that makes some people feel more valuable and in some ways it makes them feel less valuable, right?

Allison: In some ways they feel like, cool, I can offload all of this stuff to AI, which means that I can operate in my zone of genius, in my like strategic, like in the space that I love more.

Allison: And for some people, it's actually like, I love these things and actually like, it makes sense to offload these things to AI.

Allison: And so the stuff that I'm doing, some of it I love, but a lot of it, you know, feel like just feels, feels different.

Allison: And I think smaller teams, people working more independently, a little bit in silos and not always on, sometimes it can feel like, oh, I'm just managing this machine as opposed to like crafting in other ways.

Allison: I think that's also going to lead to lower morale and lower, right? And all of the poll surveys, it's like, do I feel like I contribute to the company's goals?

Allison: How do I personally see myself in the progression of the company and where it's going? And I think it's going to be harder to see that.

Allison: And so I think a lot of companies are also going to have to invest in workshops or part of those offsites or whatever that help people think about helping people love the new shape of what they do.

Allison: And what that looks like and what that, how they sort of like see that value or increase their, their morale through communication, through camaraderie, through connecting with other teams or, you know, sort of whatever that looks like.

Allison: I think, I think, I think we're going to get to a bad place quickly.

Allison: And then I think I would not be surprised at all if that's the kind of work that people are like, oh, we have to do this offsite or we have to like help our team communicate more effectively.

Allison: This is why, or like we have massive attrition because nobody sees the value. Like we've blown more out and nobody sees the value in what they do anymore.

Allison: Um, I think those sorts of like parts and pieces is what in the next 12 to 18 months, I think I'll get calls about.

Jeremy: I think it makes, yeah, it makes sense to me.

Jeremy: Like I think about like the number of developers I've talked to who are either experiencing burnout or being, you know, feeling burnout right now or have in the past, you know, few months, the, you know, sort of the disillusionment about what their jobs are right now.

Jeremy: The grieving process in some ways, even with some, some excitement.

Jeremy: And there are certainly some people that are extremely excited, but I would say most developers I know that actually like programming are sad about what they've lost and don't feel as connected to the work.

Jeremy: And it seems like in good jobs, um, people either love the craft that they're doing. They love the mission that of the, who they're serving or they love their team.

Jeremy: And if we lose craft, if we lose craft, then you have to bump those other two somehow, I think. Like, and you don't get to like, if you're in a company, your mission's probably stuck.

Jeremy: So what do you do about team is feels like that's where it has to, has to go, has to come from.

Allison: Yeah. And team is naturally going to fade away because again, like you're, instead of asking your team a question, like you're going to AI, which makes sense because it's faster and you get a better answer.

Allison: Like, I don't think that people shouldn't be doing that, but it means that, yeah, there's going to, they're going to feel more, more disconnects in a variety of these areas.

Allison: And when you connect all of those dots, burnout, attrition, right?

Allison: All of these like super negative business outcomes that I think a lot of people are going to be like, well, how do we still encourage AI usage, but guard against those things?

Jeremy: Yeah.

Allison: And that's like, that's where I come in.

Jeremy: Yeah. Yeah. Job security.

Jeremy: I hope that people like, it always feels like you can sort of have a pessimistic view that companies just won't see how like that, that's the answer, you know, that, um, like that connect, seeing the difference between a really well connected team and a really disconnected team.

Jeremy: Like there's such a stark contrast, but if they don't, if they don't grasp that organizationally, um, it sort of worries me, but I guess that's,

Allison: yeah, that's where I'm sort of like, we'll see. That's where I'm like, I think that that's where I'm going to get phone calls, but it could be, right? But it could be like, nope, doesn't matter.

Jeremy: Yeah.

Allison: It doesn't matter to us. People are shipping where, you know, company milestones are being met. It doesn't like attrition doesn't affect us that much, you know, whatever it is. Yeah.

Allison: Um, so yeah, very possible that it's like, sure. We recognize this, but we don't see the need to like spend money on it or do anything about it. So,

Jeremy: but sometimes people hire you thinking they need to solve one problem and then they find out there's another more, you know, clear root cause. So, uh, hopefully it's that too.

Jeremy: And being persuaded of those things.

Allison: Yeah.

Jess: Allison, it's time for us to bring our time to a close, but, um, it's been so wonderful to get to meet you and to learn more about your business.

Jess: Uh, you've had an amazing career and, uh, it's, it's super exciting to see what you're doing to, to help engineering teams and, um, what, what an exciting place to be for you.

Jess: So thanks for sharing that with us. And, um, before we leave, uh, how can we help you out? Is there anywhere we can point people and also let us know, can we see you in real life sometime soon?

Jess: Are you going to be at any conferences or in person anywhere?

Allison: Oh, um, where you can find me online, uh, is my website is the, the... of course, as a good engineer, I have like 18 domains to, you know?

Allison: So, uh, it is Allison McMillan.com or, um, Daydreams in Ruby, uh, cause it started as my, my original place that I was blogging as I was becoming an engineer.

Allison: Um, so daydreamsinruby.com and then the best place, you can find me on most social media platforms.

Allison: The best place is LinkedIn, look for Allison McMillan, uh, or Tavlin Consulting as well. Um, and then where am I in the future?

Allison: That is such a great question.

Jeremy: It depends on when Claude comes back with the CFPs.

Allison: Yeah. Um, no, I'm trying to, I'm trying to think, um, I don't know if I have any, well, I'm doing the Walk Shop in Patagonia, which is, is sold out.

Allison: Um, but that is taking up a good, a good fun chunk of my, uh, of my November.

Allison: Um, so I'm not sure that there's anywhere specific by the time this, this episode comes out, but you know, I'm always around the tech conferences and the internet and podcasts and et cetera.

Allison: So, um, I'm sure that you will see me in person somewhere soon.

Jess: Yeah. Be sure to ping us if you are planning on being anywhere.

Jeremy: Yeah.

Jess: Be sure to get it out.

Jeremy: Awesome. Thanks. Thanks, Allison. This has been great.

Allison: Yeah. Thanks so much for having me.

Creators and Guests

Jeremy Smith
Host
Jeremy Smith
Product-focused Rails dev • Studio: http://hybrd.co • Organizer: https://blueridgeruby.com/
Jess Brown
Host
Jess Brown
Indie rails dev since 08, currently building CSePub & TRACT. Co-host https://t.co/TpDORNDqZV. Family of 4, also interested in faith, crossfit, cycling, RV'ing, finance
Allison McMillan
Guest
Allison McMillan
Engineering leader. Former VPE QuotaPath. Former DEV & GitHub. Mom. Dev. Speaker. Ruby Central board member.
Allison McMillan - Designing Serendipity
Broadcast by