Section Insights
Introduction to Lovable and Nursa
What is Nursa and what is the significance of vibe coding?
Nursa connects healthcare managers with qualified clinicians for shift needs. The rise of vibe coding signifies a shift where everyone can become a builder and create applications, indicating a democratization of product management and engineering.
- Nursa facilitates connections in healthcare staffing.
- Vibe coding empowers individuals to create applications without traditional coding skills.
- The current moment reflects a significant shift in how products are built.
Empowering Employees to Build
How has Lovable changed the building culture within organizations?
Lovable has made building accessible to all employees, allowing everyone in the organization to create and ship projects, fostering a culture of innovation and collaboration.
- Lovable enables non-technical employees to contribute to product development.
- A culture of building can lead to increased engagement and creativity.
- Empowering all employees to build can lead to a significant increase in projects and initiatives.
Governance and Risk Management in Building
What are the risks and governance considerations when everyone is a builder?
The main risks include potential chaos in product quality and design consistency. However, the fear of failure can be mitigated by understanding that the worst-case scenarios are often not as severe as perceived.
- Understanding risks helps in managing the chaos of decentralized building.
- The worst-case outcomes are often overstated, allowing for more experimentation.
- Effective governance can help maintain quality while encouraging innovation.
Decentralization and Its Challenges
What are the challenges of decentralization in a building culture?
Decentralization can lead to inconsistencies in design and product quality if not managed properly. Without a central design system, projects may diverge in style and functionality, complicating optimization.
- Decentralization can lead to design inconsistencies and optimization issues.
- A central mechanism is necessary to maintain coherence in product development.
- Balancing freedom to build with oversight is crucial for success.
Overcoming Resistance to New Tools
How can organizations encourage adoption of new building tools among resistant employees?
Organizations can use strategies like show-and-tell sessions and hackathons to demonstrate the value of new tools. However, some resistance may stem from mindset issues, requiring tailored approaches to engage individuals.
- Demonstrating the value of tools through practical applications can reduce resistance.
- Mindset and curiosity play significant roles in tool adoption.
- Tailored engagement strategies are essential for overcoming resistance.
Transcript
0:00 Great, I'd like to welcome to the stage, Lauren Rhode from Lovable, Head of Revenue, and Curtis Anderson from Nursa, which Curtis, can you give a quick overview, what is Nursa? Nursa connects healthcare managers who have shift workforce needs to the qualified clinicians who can fill them. Great, so the title of our session is What Happens When Everyone Builds, I think a large part of what we've been hearing today in these conversations is really like we're at another moment.
0:26 There's always another moment, right? This is the moment we're in now, a lot has changed. I want to zoom back, it's 2023, 2024, everyone who's at Every now is now using an application called Lovable, and the rise of the vibe coder is the moment we're in then, where everybody's going to build billion-dollar businesses themselves, everyone's now a product manager, everyone's now an engineer. Lauren, I want to put it to you because I think you have more purview than almost anyone in this room around what happened to vibe coding.
0:54 Well, first of all, good afternoon, oh yeah, okay, I often have to say good afternoon twice, but we've got some good energy even though we're after lunch and a bit of a lull. Okay, so I've got a few questions for the folks in the room. How many folks have heard of Lovable? Show of hands, okay, that's great. How many folks have built something with Lovable? How many folks have built something with Lovable that is running in production that's load-bearing?
1:23 I'll say, so like, hosted is connected into some of your data sources, you have end users coming to it, a smaller subset of the audience, so we'll see if I can maybe shift a bit of perception here over the course of this conversation and share a bit with you about what we're seeing in the market that comes back to the first question you asked Brian about what happened to vibe coding? I think, Brian, when we were talking about this, it was like, let's like tear down this concept because we don't talk about vibe coding anymore, but I don't want to tear it down because I think there's this really valuable and enormous amount of pent up demand that we saw around the idea that everyone, not just engineers and technical folks, but like the 99.7% of humanity that are not software engineers, being able to build and then not just build, but actually to ship products and software, and so I think it was a valuable moment that we came through, but increasingly now what we're seeing at Lovable is people wanting to do much more, and that is what we are seeing our customers across the board. I'm really excited for you all to hear Curtis's story at Nursa, which is like just an amazing mission to put a nurse at the bedside of every patient in need, but also the way that Curtis is super forward thinking in changing the way that your company works.
2:46 So yeah, Brian, I'll go back to you. So I think part of that answer too that you're alluding to is everyone could build, but nobody could really build the things necessary for everything else to happen that might happen for building for a business or whatever. Curtis, you're part of this conversation I think because you had a very similar experience. You're founder of a company, you're building a company, you're seeing AI emerge inside of the company first as like sort of an alien force.
3:11 What was that experience like where you noticed your team was using AI, you began using AI, and the feeling of is this a good thing or is this a bad thing? What's this going to do to my company? Absolutely, first use cases kind of early stuff was all content based, so the way that we would create and write content to better help shape that. And then there was this moment where you could start to do more stuff with it. I took it home and took just a couple of days and actually just handed a handful of these new models, pieces of tech, Lovable to my kids, nine, six, and three.
3:46 So my nine and six year old oftentimes their first blush with technology starts to really help me shape the way that I can think about using it with tools at work. And then we, you knew there was going to be a there there, there's just a, this is just going to be a thing, like we're going from augmentation to automation, it felt like such a natural path. And so we started playing with it in house, we dedicated some time and resources to just test and play with everything.
4:18 And then there was a moment, about six months after that, where I had our VP of product called me and said, Lovable's had a breakthrough, they've shipped a multimodal chat with the agent. I don't know why they're not announcing it, but we've had it for 48 hours and it's like I've created a whole new product, you got to take a look at what's happening. This was on a Sunday night, late last summer, last fall, and like we had had this moment of explosive growth that was around people prototyping or maybe even vibe coding.
4:52 But Curtis, you and Nenad, the VP of product at Nursa, were at that moment of the shift where you had given him, so you were a one product company, you had given him a mission to go try to create a new product and a new business line for the company, and he called you. And will you just say a few more words about what he built and what happened in that moment for you? Yeah, absolutely, you still couldn’t dependably rely on the tools, there's some in the broader spectrum of total engineering, pipeline and lifecycle, it wasn't quite there and so the idea was, well, if we're going to get there first, we need to do this in a vacuum with a new, with a new product of some sort, it's got to be on its own. And we, you know, we help get nurses to the bedside of every patient in need, like you said, upstream from, you know, how does a nurse get created is in a school, a program of some sort, and we've always thought it would be really interesting to help those folks because part of what they need to do is get clinical hours, internships, in different facilities, and so what if we built a product for students that would help them accelerate that path, better connect, and so Nenad called and said, like, I've got it, like, so it was this target on a road map that we knew we wanted to get to at some point, but not pressure sensitive, and so we just used that as the mark, and it's been an incredibly compelling piece of our broader expansion this year.
6:25 There's several thousand students now on leveraging the product, and 15 months ago it didn't exist. Amazing. It's amazing. Who inside of your organization's building now? Yeah, so as soon as we did that, after that Sunday night, I think the quote on the website is that I said to Nenad, “Everything’s changed”, we got to rethink this, and so for me, what that moment for Lovable became was this illustration where anybody who's scared of a command line terminal, anyone who pukes when they hear the word code, this is now an approachable half step.
7:05 It's an environment where they can play, they can ship something, and it's safe, they're not going to, it protects them from themselves, so to speak, and so very shortly after that, we gave everyone access to Lovable. Everyone at the company has shipped something. Since then, it's about a hundred and sixty person org today, and everyone has built something. We've got thousands of projects in the Lovable instance today. Brian, can I maybe jump off that?
7:36 There are a couple things that Curtis did that I think are helpful, like number one, Curtis, you had that aha moment, you said the world has shifted, and you brought the company together, and you said, you're a builder, and you're a builder, and you're a builder, and I guess, you know, I want to ask you a bit about what gave you that conviction, but I'll just share what I'm seeing across now thousands, actually hundreds of thousands of companies of all sizes that are building with Lovable is there are a couple of models.
8:05 One is leadership direction from the C level to say, you're a builder, you're a builder, you're a builder, and put a capability like Lovable into the hands of 100% of the knowledge workers in your company, and then we have a strong perspective and a lot we've done in product to give you the governance layer and control plane to understand what everyone is building, and to be able to promote or harden into production like the things that are the best ideas, built by the people who are closest to the problems and not needing to wait on a central IT or engineering queue necessarily, so there's a lot more we can talk about about that model. We're also seeing some companies, it's really a bottoms up grassroots movement that they're starting to identify specific applications to replace in the company, and then it comes up to leadership, so there's a lot more that we can talk about there.
8:55 I will just share one example within Lovable ourselves is we've got a command center called Catalyst that all of our account executives and customer success managers and solution architects use to run every day that sits on top of our CRM and all of our data, and Michelle Fitzgerald is in the audience. Michelle is an AE on our team who was the person who actually built the first iteration of this. She said like I've got this pain and for folks who have sales people on your teams who are jumping between a ton of different interfaces and applications it has become really challenging and the sales tech stack has proliferated pretty wildly. So it brings us all back into one place, but built by someone who is closest to the problem and then hardened by our RevOps team.
9:37 So I guess Curtis, is there just anything else that you've thought about? I mean, you've got some both things that you might expect of software applications that you've replaced on the order of now over a million dollars you've saved, but also you've got like some folks who might be very surprising who have built meaningful things. So just to continue on that on the sales pipeline piece, we have an accountant, a CPA who shipped a very similar tool to what Michelle built internally for us, manages commissions, ties things together better than ever before, pulls in context from a CRM and there's a couple of MCPs and harness on the back end of that that feeds it, but built uniquely for your business.
10:21 Totally. And by an accountant, which is incredible, he's a great kid. We've got a retired parole officer who put together a credentialing application, a ton of what we do, we have to get the nurse there very quick, less than 24 hours before the shift and so we have to do a lot to verify who that individual is very quickly in a very short timeline. And this parole officer had a ton of context about that, had never touched code before, picked up Lovable, and look, nothing about what they built would make a back end engineer proud, but it started an acceleration towards a solution that now is live, dependable, and we all use.
11:06 And so in this era, your competitive advantages are speed and context and that matters a great deal as I think about how we're going to perpetuate the existence of Nursa long into the future and why, why we would give all these individuals these tools. But yeah, to your point, Lauren, the cost savings are real. In the last 15 months, we've cut more than a million dollars in non-head count, OpEx spend.
11:37 Our reliance and dependence on third party vendors has dropped by more than 80% and we're just getting started. So you've got a parole officer, you've got an accountant, I'd love to kind of get brass tacks on what needs to be true for you to actually allow people with those backgrounds, non-engineers, et cetera, to build things that you’ll Yeah, actually take to I think production and there's try to run business around? certainly a component of this that's culture, for sure.
12:12 The proactivity tolerance for ambiguity or uncertainty in your culture is, I mean, that's just sort of born and bred in what we do, some of that is the nature of the stage of company that we are. But outside of that, you've got to have people who, you've got to have the the way space where you that can protect it. So Lovable these governance layers and has rapidly expanded, has really mirrored our own ramp into this.
12:42 And so the speed at which they're launching these tools, expanding these tools, like we just haven't outpaced it yet, which has been really remarkable by way of having a partner of that capacity. And then, furthermore, you've got to have people that have access to that context. And oftentimes, that's another governance question, for sure. But for us, like the questions are, you know, what are the risks? Like, what's the worst-case scenario that can come from this? I think the first answer to that is always that somebody could die, and very rarely is that the actual potential outcome.
13:18 And so then, like, at a worst-case scenario for us, we end up being a bad example for somebody else, and that just felt like a really low threshold to start to get the rest of the team involved. That's a bit of, like, how you got over the fear as well. I mean, this is, yeah, just like framing. What's the worst that could happen? And then, actually, what's the best that could happen? Yeah. And if you really believe the prospect that context matters in a competitive advantage or the speed at which you move, well, then you have to say to yourself, like, then we're going to start making bets on that.
13:52 Like, we're going to start using this. And as the implementation cost comes down increasingly and asymptotically, then we got to put it in the hands of people who know the customer, which is a really, I mean, never in the history of software has identifying the problem for the customer, been the hardest piece, right? We put product and design and sort of all of these orgs in place. As an insurance cost for every time an engineer's hands is on a keyboard, we know with a very high degree of certainty that the output is going to be impactful for the company.
14:30 And that's just not true anymore. And so getting the tools to the people, certainly, even just as a cost mechanism, is much, much less risky than it has been historically. How has that changed, you know, your position as an executive, allocating resources, capital, attention, et cetera, walk down me from one, where are your dollars and your time going and with whom? And then how are you thinking about the other things that you need to kind of waterfall down from a hiring perspective?
15:03 Are you hiring differently, different kinds of people? Yeah. I haven't shipped this much code since the first year of the company's history. And we've, you know, we cover more than 600,000 clinicians across the country, relationships with more than 5,500 facilities. It's not a, like, we're not a pirate ship anymore. There's a lot to mourn about that. So if you're in that phase, just love it while you're there. These days will be gone. But for me, and I'm really, really biased in this.
15:39 If you're an executive and you don't have your hands on these tools, like, you're, I just think you're done. You're, you're so cooked. You're so cooked. Because it's like, if you, if you had been around at the turn of the century and you tried to explain as an individual contributor who had been on a plane to an executive who had only ever been in a car, the power of what flight could do, like, it's, it's really hard to do, like, if you're not in this game, if you're not feeling it, you know, Dan talked earlier about the changing models and switching costs and sort of how quickly this is all happening.
16:18 I got, organizations are flat. You got to know your business from the inside out. And I think at any level now is the time to start doing that. And so I, I'm really anchored on that end of the spectrum. The way that we hire, I mean, I now start the interviews with two questions. Like, give me as many examples as you can of places where you've had to deal with ambiguity and what you did with it.
16:45 And tell me all of the stories about things that have happened in your life that should have killed you, but didn't. And if you have willpower, demonstrated willpower, and you can tolerate ambiguity, like, this is, this can be your home. And we can give you tools to sort of fill in the gaps and the, and the right pieces to, to, you know, to be able to succeed. Great answer. One more, one more question, then we'll open up to the audience.
17:12 Lauren, from your perspective, seeing again thousands of companies, I've probably not no companies like Curtis, exactly, but what have you seen successful companies who have oriented their business around everyone being a builder and everyone being able to unlock more value and kind of extend themselves more? What's been successful pattern wise in terms of how those companies operate, how those executives lead? Yeah, so we're seeing a few different patterns emerge around how we think about, just like, again, putting the power into the hands of everyone out at the edge of the enterprise to be able to build, but with guardrails and structure and prioritizing the problems to solve and then promoting the best solutions into production.
17:56 And it comes back, you know, the the best examples, common theme is someone like Curtis within the organization to embrace and say not only what could go wrong, but what could go right here. And, you know, one of the things that we will often do if we, if there isn't a leader who has that, that vision is lead a hackathon or a buildathon and set out some specific problems that the leadership wants the team to solve so that it's not running out into all kinds of directions, but we got some targets. And what we're seeing is, in many cases, it's actually either interns or folks who are super tenured, who've never had the experience to build, but, like, deep subject matter experts, your parole officer, your accountant, who are emerging with the best ideas and the best solutions.
18:46 So that's one of the things that we're doing. And then there's a lot that we have built into the product to help, again, give leaders the ability to see where there are maybe multiple people trying to solve the same problem and then be able to turn that, again, into products and applications that will run workflows across the company. So there's a bunch there. We have a few different models for folks who are interested more than happy to chat afterwards as well. But, yeah, just incredible, incredible moment in time and, like, the greatest change moment in human history.
19:22 That's great. Questions? People with microphones. Why don't you choose, since I'm looking a little into the dark. There we go. Hi. Huge fan. Believe in the power of all this. That's why I'm here. And the title of all of this was what happens when everybody's a builder. And I'd love your thoughts on the flip side of that meaning. The sheer load and the mass of stuff that's coming in our way. The full-on embrace of more is better and more and more and the action orientation of that and all that stuff and where it could lead versus less and taking away.
19:59 And some of us had, like, really interesting conversations based on this. Just curious, like, how do you think about that? Yeah. Do you want to take it first? Yeah, go for it. Yeah. I might be a little bit biased here. We've added seven new lines of revenue this year. We've extended the engineering team to everyone in the org. And so the flip side of that, there's still these conversations that we have about how to orchestrate that.
20:27 A good example is, like, most teams will have some kind of a design system. And if there is no central mechanism to anchor what the design system is, if everyone can ship to that, what's the outcome? Well, a button goes from red to green to blue to, and that messes up optimization. And you sort of see the dominoes tipping. So I think there's decentralization. The biggest risk that it has is that it's decentralized. And so if everyone can build then what matters?
21:01 And I think some of that is just, you know, perspective orientation. It's taste. Because there's this really big industry example in film for a long time where Netflix was dumping billions of dollars into content quarter over quarter over quarter for a year over year over year. And Warner Brothers was still in this world where they had a four panel. Like, their audience was men over 18 and under 18, women over 18 and under 18. And Netflix won, in that case, the data plays out.
21:34 You can now build a story very cheaply for kids who play football in Oklahoma and get your money back, get a return on that. And so, yeah, you get a lot more stuff. But there's no extra weight from that stuff. And we actually get to personalize much, much more deeply in the way that products can touch human lives and connect with users. So I'm, again, I'm sort of, I just don't think think there's a downside some of here, but the I risks are that decentralization is unstructured.
22:13 And that has very natural consequences. You are out on the edge of someone who has a very high appetite and high tolerance for also noise because you think that beautiful and creative things will come from it. And I think, like, I mean, comes back to some very simple basics for me. So I would how do think we about people, empower process, and technology. And and so, number one uplift is more of our people and make sure that folks aren't getting left behind in this moment. But then just one data point that I'll share, to some extent to your question, is that we see, on average, people build 4.7 disposable apps in Lovable before they build something that is load bearing or, and, yeah, shipped into production.
22:58 And so it's like, how do we actually give people the freedom to that creative space to be able to get to that meaningful output? And that's across now over 70 million projects that have been built in Lovable. So looking across that data set. And there's the process that we wrap around it so that we don't just have all of these ideas that are floating about, but we have some structured decision making. And what we're thinking a lot about is how do we build into our technology and product ways for you to be able to, for humans to be able to see and sort and understand the themes of what are getting built.
23:31 So, and helping you to deduplicate or even in the build process, telling someone who's building like, hey, actually, something like this has already been built. Do you want to go look at that before you continue to build? So there's a lot of responsibility that we feel we have in the technology to help you be able to help our humans and people be able to manage that potential proliferation. There's like, there's real value in it. We just like, we believe in that and then we want to give you the tools to be able to manage and guide the best ideas.
24:03 I think part of your question is about quality too. It's a sense of just because there's a lot of stuff doesn't mean there's better stuff or good stuff. I think quantity, at a certain phase of anything, quantity has a lot of its own quality, which is it's the way you get reps, it's the way people learn how to use tools. I agree with you. I think at Every we take this very, very seriously where this concentric idea of quality of personal benchmarks, which Mike just gave a talk on, is ultimately about not measuring models based on what they can do, but based on what they can do specifically for the work that you do with your standards in mind.
24:35 You kind of step out of that to the team level and it's not what technology can do for your teams. It's how much of your team's expertise and quality is able to be cross-referenced with each other and work together without needing to add the coordination cost together. At an organizational level, it's the quality of how much tolerance do we have for the ambiguity from the top down across the whole org so that those reps in the first two concentric circles can actually fit into play. And so the real question there is just sort of like where does quality, who holds the standard and how does the standard, is the standard empowered?
25:09 And I don't even want to say enforced, I think it's more empowered. You have a right to your quality bar in all of these domains. And quantity is at this stage, burning tokens right now as much as it's sort of, and just creating stuff that we're going to burn down two weeks later because we find out we couldn't quite do it. It's still part of us finding our way towards the quality line that we want to maintain. That's the Every, Every kind of like argument we internally have a lot around this. Any other questions?
25:33 Yes. Thank you for that question. That's very thoughtful. Hi, yes. So one thing that I really love the story about the CPA, coming in, building something that inherently created value that maybe a product manager and engineer wouldn't be able to think of because they're not that subject matter expert. And I think that's amazing. And I think that has showed AI can be an unlock for folks to be able to do that at scale. The problem is that, and I've noticed, is just because you have the tool, does not mean that naturally happens within an organization.
26:04 Some things that I've noticed that have helped a ton is show and tell, or hackathons, or things to be able to show folks like how you can apply this technology. But the problem is, is that even if you do that, some folks are still super resistant, even engineers. And it's fascinating to me that it could be a mindset thing. Like, we always hear about, are you curious? But, you know, also, like, have you found the one thing that has clicked?
26:28 And that's one thing that I'm struggling with with certain folks. And it's sometimes easy to probably just say, like, give up and be like, well, maybe this is, like, am I going to continue my time? But I don't want to do that. But the reason where my question is going is, in situations where folks are resistant still, even if they have the tool, even if you've done all these things, are there things that you have done that have been successful, that have turned those folks that are resistant into folks that are now empowered and champions of the technology?
26:58 Yeah. Curtis, would you mind sharing your three flavors of optimism? Or wherever your mind goes, but we've, like, we've jammed a bunch on philosophically, even at Lovable, and we've got very high caliber talent that is at Lovable because they really want to be a part of it. But even here, there are, like, flavors and shades of how far can we push this everyone-is-a-builder mentality, and what are the trade-offs of doing that, but also for me, in our go-to-market org, I set a standard that we need everyone in the team to, over 60% of their time to be out in the field with customers.
27:36 And so how do we even just give some guidance for the people who want to be building all the time to be also working on the things that are most important, but maybe three flavors of optimism and whatever else comes to mind for you? Yeah, I'll just acknowledge now, in my career, I've never encountered a technological step forward that has been more polarizing or more illustrative of the idea that you can drag a horse to water, but you can't make him drink.
28:05 And so when we approached this, there was sort of this moment where we had the product. Nenad and I had finished building the product. We, both of us are forward-leaning, and we're ready to sort of trust this thing out in the wild, but we knew that to a more conventional engineering mindset, this was going to be heresy. And so, I decided I would do three things. We were going to change every team member's focus.
28:38 We were going to change every team member's team, and I was going to clear my calendar for six months and we were going to sit with everyone. I was just going to repeatedly go back into these teams and sit with them because the only thing that I've ever figured out that will accelerate the speed of trust in a transition like this is actually getting in the trench, getting shot at by the same enemy, and having a leader still with you when sort of the fog clears.
29:04 And so we did it, and the second day after we did it, the first day I had four people quit. All four of them independently told me, I don't think you're wrong, I just don't want to do this with my career right now. And we said, God bless you, and Godspeed, and out the door they went. And the second day, I had a product manager who built a project in Lovable that had just flaming fires from hell with a countdown to the date that I had given them on an impossible deadline.
29:34 So literally the first thing that came out of the coffer was this mutinous thing. And so I had this, in the next town hall the next week, I had this slide that talked about three flavors of optimism. I said, guys, some of these changes will be good, and they'll stick, some of them won't. But here's what I need you to realize, like, I'm committed, we're doing this. And if you think that Nursa has been a great ride so far, then, boy, do I have news for you, we're just getting started. If you think this has just been a mid-run, then there's never been a better time to sort of reset expectations, and I need your help doing that. And then if you just think that we're nearly dead on the table, then, like, what a great way to just shock the system, and so come with me.
30:22 Now, for six weeks, like, we shipped almost nothing. And then every week thereafter we climbed, and on the smallest version of the team that we have ever had, we shipped more code in six months than we had done in seven years. And so yeah the first guy through the wall gets bloody. That's it. And Like, that's so just... That's it. you have to find people in your organization who you can catalyze around that idea, and leaders who will go the distance with you.
31:00 You really start to get to know a teammate when their back is against the wall, and there's no real data to suggest that they're right. Like, those are the kinds of bets that change things, and I think this room is probably full of most of those people. And so, if you really don't feel like you have anybody like that at your org, you're probably at the wrong org. I think that's a great place to end it.
31:28 Lauren, Curtis, thank you so much.
Summary
- Nursa connects healthcare managers with qualified clinicians, aiming to improve patient care.
- The rise of "vibe coding" reflects a trend where non-technical individuals can build and ship software products.
- Lovable empowers all employees to become builders, fostering a culture of innovation and collaboration.
- Curtis shares his experience of integrating AI and building new products at Nursa, highlighting the importance of context and speed in competitive advantage.
- The shift to a decentralized building approach requires governance and oversight to maintain quality and coherence.
- Successful organizations encourage experimentation and provide structured frameworks to guide innovation.
- Curtis emphasizes the importance of leadership presence and support during transitions to foster trust and collaboration.
- The discussion highlights the need for a culture that tolerates ambiguity and encourages proactive problem-solving among all employees.
Questions Answered
What is Nursa and what is the significance of vibe coding?
Nursa connects healthcare managers with qualified clinicians for shift needs. The rise of vibe coding signifies a shift where everyone can become a builder and create applications, indicating a democratization of product management and engineering.
How has Lovable changed the building culture within organizations?
Lovable has made building accessible to all employees, allowing everyone in the organization to create and ship projects, fostering a culture of innovation and collaboration.
What are the risks and governance considerations when everyone is a builder?
The main risks include potential chaos in product quality and design consistency. However, the fear of failure can be mitigated by understanding that the worst-case scenarios are often not as severe as perceived.
What are the challenges of decentralization in a building culture?
Decentralization can lead to inconsistencies in design and product quality if not managed properly. Without a central design system, projects may diverge in style and functionality, complicating optimization.
How can organizations encourage adoption of new building tools among resistant employees?
Organizations can use strategies like show-and-tell sessions and hackathons to demonstrate the value of new tools. However, some resistance may stem from mindset issues, requiring tailored approaches to engage individuals.