Jeitinho — Finding the Creative Way Around the Obstacle
When a Brazilian colleague hits a rule, a flat “no,” or a bureaucratic wall, the instinctive first move is not to follow the procedure or escalate it formally — it is to find a clever, personal way around it. This is the jeitinho: a resourceful workaround that treats obstacles as negotiable rather than fixed. If a form cannot be processed, someone reframes it; if a deadline looks impossible, someone finds an angle. It is improvised and usually friendly, since charm and goodwill are part of the technique. In practice this means that when you tell a Brazilian colleague something “can’t be done,” they often hear “let’s find another way.” Don’t read it as disrespect for rules; it is a problem-solving reflex. If you want a fast solution, present the rule as a shared obstacle to get around together, not as a verdict.
Personalism — Resolution Flows Through the People You Know
In Brazil the route to solving a problem usually runs through a person, not a system. The first question a colleague asks is not “what’s the process?” but “who do I know who can help with this?” Resolution flows through relationships — a contact in the right department, someone who owes a favor, a friend of a friend. This is why Brazilians invest so heavily in building and maintaining personal ties before they need them: the network is the infrastructure for getting things done. In practice, when you are stuck, the fastest path is usually to find the colleague who knows the right person rather than filing a request into an impersonal channel. Relationships are not a courtesy layered on top of the work — they are the working mechanism. Cultivate them genuinely and early, and problems will resolve that the official channel could never move.
Cordiality — Keeping the Relationship Intact While Solving the Problem
Brazilians tend to work through problems with warmth and indirectness rather than blunt confrontation, because preserving the relationship is part of solving the problem. An issue — especially one that touches a person — gets named gently, softened with diminutives (“é só um probleminha”), wrapped in friendliness, or raised obliquely instead of as direct blame. A hard “no” or public criticism can rupture the personal bond that actually makes resolution possible. In practice, “vou ver isso” (“I’ll look into it”) can be a polite no, and openly criticizing a colleague usually backfires. To surface a real problem, do it warmly, privately, and indirectly, protecting the other person’s standing. Read the affect, not just the words. The aim is to fix the issue without anyone losing face — and the warmth is not empty politeness, it is how the work gets done.
Improvisation — Solving It As You Go
Brazilian colleagues are often more comfortable solving a problem in motion than planning every step in advance. The underlying confidence that “vai dar certo” (it will work out) licenses an adaptive, in-the-moment style: start, see what happens, adjust, find the opening — much like the improvised flow of Brazilian football. Detailed upfront plans are treated as provisional; the real solution is expected to emerge through skillful, flexible response as the situation unfolds. In practice, don’t read a light plan as carelessness, and don’t expect rigid adherence to one when circumstances shift — colleagues will adapt, and often outperform a fixed script. If you genuinely need a fixed sequence, say so explicitly. And when things go sideways, expect people to stay calm and improvise a path through rather than freeze. The strength here is adaptive resourcefulness under uncertainty, not advance choreography.
Gambiarra — Making What You Have Do the Job
When tools, budget, or supplies fall short, Brazilians improvise a working solution out of whatever is at hand — this is the gambiarra. It is the makeshift fix that keeps the machine running, the workaround built from spare parts, the resourceful patch that stays “temporary” for years. Born from long experience of scarcity and unreliable supply, it is both a survival skill and a point of pride; there is real satisfaction in solving something with ingenuity rather than money. In practice, expect colleagues to reach for a clever, low-cost adaptation before requesting the “proper” resource, and don’t dismiss the makeshift result as sloppy — it often works and reflects genuine skill. If you actually need the polished, durable version, specify that clearly, because the default instinct is to make do impressively with what is already available rather than wait for ideal conditions.
Tacit Knowledge — The Solution Lives in People, Not in Documents
In Brazil, the knowledge of how a problem was solved usually lives in people rather than in written procedures. Solutions are passed along by showing, telling, and doing alongside someone — the way crafts, football, and capoeira are learned — far more than through documented process or manuals. Don’t expect a tidy written record of how something was handled last time; expect that the person who handled it carries the know-how in their head and hands. In practice, the fastest way to solve a recurring problem is to find and ask the colleague who solved it before, not to search a system for documentation that may not exist. Build the relationship that gives you access to that tacit knowledge. And if you need something captured in writing for the future, you will usually have to ask for it explicitly and explain why it matters.
Aspirational Pattern — The Ideal of Systematic, Documented Method (What Colleagues Aspire To, Not Necessarily How They Work)
Note: this describes an ideal that Brazilian organizations hold and teach, not how problems are typically solved in daily practice. Brazilian professional culture widely espouses systematic, methodical problem-solving — formal root-cause analysis, documented procedures, quality methodologies, structured project management. You will hear this language in meetings, see it in official process maps, and find it taught in training and engineering programs. It is sincere as an aspiration and signals real respect for rigor. But it frequently diverges from everyday behavior, which leans on improvisation, personal networks, and creative workarounds. In practice, treat formal methodology as what colleagues believe they should do and will present officially — while the actual resolution often moves through the relational, adaptive routes described in the other patterns. Knowing this gap helps: invoking the official process may earn nods, while the real solution still runs through people and improvisation.