BUILD AGAINST
CONSENSUS

Vélez enjoyed investing and learned from strong entrepreneurs, but proximity to builders did not satisfy his desire to own the consequences. He wanted to make the hard decisions rather than recommend them from across the table. A career can be educational and prestigious while still keeping you one layer away from the work you most want to do. Notice whether your energy rises when analyzing a problem or when carrying responsibility for the outcome. The answer does not make one path superior; it clarifies which form of contribution fits you.

Starting a company can consume decades, so Vélez asked what problem could justify that commitment. Banking stood out because even a modest increase in competition could affect a large system and many customers. Match the scale of the problem to the scale of the life you are prepared to invest. This does not mean every founder should chase the largest market. It means comparing opportunities by consequence, duration, and personal fit—not only by ease of entry. The right question is not just whether an idea can work, but whether success would matter enough to sustain the years required.

Experienced banking leaders gave Vélez serious reasons not to enter the market, alongside objections rooted in fear or assumptions from an earlier technological era. His response was neither obedience nor reflexive defiance. He listened, decomposed each argument, and tested whether its premise still held. Treat expert rejection as a bundle of hypotheses. Keep the regulatory, capital, or operational constraint that remains true; discard the conclusion that depends on yesterday’s infrastructure. Contrarian judgment becomes credible only when it can explain precisely which condition changed and which risks did not.

A regulatory change threatened to make Nubank’s original launch schedule fatal. The team compressed the plan, and Vélez describes flying an approval document to Europe because a courier would take too long. The precise dates in the captions are inconsistent, but the operating principle is clear. When a real deadline determines whether the company can exist, reorganize around the constraint. Remove work that does not protect survival, put decision-makers next to the bottleneck, and choose the fastest lawful route. Urgency is useful when it is tied to a specific failure point—not when it becomes the company’s permanent emotional climate.

Nubank initially rejected industry experience to avoid reproducing incumbent habits. That helped the team reinvent important systems, but it also created bottlenecks and unnecessary reinvention. Vélez later favored insiders who could still think like beginners—people with more questions than answers. Innovation needs both permission to challenge the system and memory of why parts of it exist. Build teams where outsiders expose assumptions and experienced operators reveal hidden constraints. The hiring signal is not ignorance or tenure; it is the ability to bring relevant knowledge without treating precedent as destiny.

Vélez created Nubank’s culture deck immediately after the fundraising deck and co-designed it with the first employees. The point was not polished employer branding. It was a short constitution that could guide hiring, performance, product, and customer communication before habits hardened. Founding teams are already designing culture through repeated decisions, whether or not they name it. Write the few principles that should survive growth, define the behaviors each principle requires, and let early teammates challenge the wording. Shared authorship makes the standard easier to understand—and harder to dismiss as a founder’s slogan.

As Nubank grew, Vélez continued presenting the culture deck to each incoming group rather than delegating the ritual. His presence signaled that values were not an HR preface to the real work; they were founder-level work. Leaders reveal priorities through what they repeatedly spend time on. Identify the few messages whose meaning degrades when outsourced, then create a durable cadence for transmitting them. Personal involvement does not require controlling every interpretation. It means supplying context, answering hard questions, and showing through attention that the standard applies from the receptionist to the engineer—and to the founder.

A missing payment reminder caused more customers to pay late, which increased fee revenue. Nubank restored the reminder and returned the affected fees instead of treating the bug as a profitable discovery. That decision translated “customer obsession” into an economic sacrifice the organization could see. A value becomes credible when it costs something in the short term. When revenue rises because customers are confused, delayed, or nudged into an avoidable mistake, investigate the mechanism before celebrating the metric. Returning undeserved gains can protect trust and teach the company which kind of growth it refuses to monetize.

Vélez argues that the ownership of Latin America’s digital future depends partly on whether the region develops enough engineers, product builders, and entrepreneurs to reinvent its own industries. He connects that capacity to where value and opportunity will accumulate. Talent is not a downstream hiring problem; it is infrastructure for economic agency. Companies can contribute by training apprentices, widening access to technical work, creating credible entry roles, and sharing practical knowledge. The point is not isolation from global firms. It is ensuring local builders can participate meaningfully in creating—and owning—the systems that reshape their communities.

Nubank’s original commitment to a completely flat organization produced slow consensus and blurred accountability. Vélez changed his view: hierarchy can coordinate large groups, but status perks and executive theater corrupt its purpose. Design authority around decisions and outcomes, not ego. Give autonomous units a clear leader, invite broad input, and identify who must decide when agreement does not arrive. Then remove privileges that cannot be connected to better work. The test for every layer, title, office, or ritual is simple: does it improve judgment, speed, or responsibility—or merely display rank?

Vélez closes with a lesson from Stanford’s interpersonal dynamics course: companies, teams, families, and every important collaboration are made of relationships. Technical judgment and strategy travel through the quality of those bonds. Relational skill is operating capacity, not a soft extra. Learn to hear what is not being said, give difficult feedback without humiliation, and reveal enough uncertainty for others to speak honestly. Self-knowledge and vulnerability do not replace standards; they make trust strong enough to sustain them. The larger the organization becomes, the more its abstract systems still depend on conversations between people.