Web Summit: 테크 박람회는 소프트 파워의 도구가 되었는가?
테크 박람회를 무대 너머에서 읽는 법을 다룹니다. 누가 주최하고, 누가 비용을 대며, 왜 하필 그 도시에서 열리는지 묻습니다. 2026년 리스본 Web Summit 개막식과 포르투갈, 카타르, 브라질, 중국의 사례를 통해 쇼케이스, 네트워크, 편집상의 결정을 구분해 봅니다.
읽기테크 박람회를 무대 너머에서 읽는 법을 다룹니다. 누가 주최하고, 누가 비용을 대며, 왜 하필 그 도시에서 열리는지 묻습니다. 2026년 리스본 Web Summit 개막식과 포르투갈, 카타르, 브라질, 중국의 사례를 통해 쇼케이스, 네트워크, 편집상의 결정을 구분해 봅니다.
읽기누구나 다른 직무의 일을 할 수 있다면, 누가 무엇에 책임을 질까요? 이번에 출간된 책의 답은 가랑(Garant)입니다. 각 영역마다 그 일관성에 책임지는 사람이 있되, 모든 것을 승인하거나 직접 하지는 않습니다. 자율성을 혼란 속에 흩어 버리지도, 승인 절차 아래 가라앉히지도 않고 지키는 방법을 얻게 됩니다.
AI 에이전트가 코드를 쓰면 테스트는 통과하지만, 업무 로직은 조용히 어긋날 수 있습니다. 같은 개념에 이름이 둘 생기고, 규칙이 깨지고, 폐기한 개념이 되살아납니다. 코드에서 추출한 온톨로지를 개발 전에는 의도와, 개발 후에는 생성된 코드와 대조하면 이런 이탈이 드러나고, 의도된 변경과 오류를 구분할 수 있습니다.
"단순하게 하면서도 데이터를 신뢰할 수 있게 만든다" 같은 종합은 모두를 납득시키지만 진짜 제품 문제를 지워 버립니다. 고객 피드백을 하나하나 원본 그대로 두고, 카드 한 장에 아이디어 하나만 담고, 긴장 자체를 독립된 아이디어로 적어 두면, 불편한 모순이 설계 질문으로 바뀝니다. 그리고 본래 매끄럽게 다듬는 경향이 있는 AI가 오히려 그것을 막는 안전장치가 됩니다.
같은 보안 질문서에 열 번째 답할 때, 모든 것을 다시 하지도 않고 틀린 답변을 복사하지도 않는 방법이 있습니다. 사실을 주제별로 정리하고 출처, 날짜, 한계를 함께 남기면, 115개 질문짜리 질문서도 10분 만에 80~90%가 준비됩니다. 그리고 빠진 부분은 담당 팀에 보내는 구체적인 질문이 됩니다.
회의 때마다 서로 아는 것을 맞추는 데 20분이 걸리고, 누군가 떠나면 인수인계는 흩어집니다. 공유된 안건은 메일을 다시 읽는다고 다시 잡히지 않습니다. 지금 어디까지 왔는지, 무엇이 취약한지, 다음 행동 하나를 담은 다시 잡기 페이지를 일하는 동안 관리하면, 누구든, 그리고 AI도, 1분 만에 같은 지점에서 출발할 수 있습니다.
한 고객에게 통했던 권고가 다음 고객에게는 틀린 답이 될 수 있지만, 보고서는 그 이유를 말해 주지 않습니다. 각 결정을 대안, 근거, 조건과 함께 남기고, 여기서 고객 데이터가 빠진 노트를 끌어내면, 컨설팅 회사는 누구의 신뢰도 저버리지 않고 배운 것을 다시 쓸 수 있습니다. 좋은 답이 더 이상 성립하지 않는 순간도 첫날부터 알아볼 수 있습니다.
AI와 나눈 대화는 결론만 남기고 이유는 잃습니다. 무엇을 배제했는지, 어떤 반론이 아직 열려 있는지, 왜 그렇게 결정했는지가 사라집니다. 이번에 출간된 책은 이 문제에 맞서 만든 작업 공간을 설명합니다. 주제마다 하나씩 두는 이 공간에서 AI는 아이디어가 어디서 왔는지 다시 찾고, 작업이 멈춘 지점에서 이어 갑니다.
서로 링크된 노트가 천 개나 있어도 전체 모습은 보이지 않습니다. 어떤 아이디어가 중심이고 어떤 것이 고립되어 있는지, 멀리 떨어진 두 개념이 어떻게 이어지는지 알 수 없습니다. 위키의 링크마다 이미 설명이 적혀 있다면, 160줄짜리 Python 스크립트만으로 완전한 그래프를 뽑아낼 수 있습니다. 탐색은 Graphify가 맡고, 걸리는 시간은 0.2초, 쓰는 토큰은 하나도 없습니다.
다음에 무엇을 검색할지, 그리고 무엇보다 언제 멈출지를 아는 방법입니다. 30개나 50개처럼 소스 개수를 미리 정하는 대신, 작지만 엄선된 코퍼스에서 출발해 구조화된 지식을 뽑아냅니다. 그리고 코퍼스가 아는 것과 모르는 것이 다음 검색을 고르게 합니다. 그 결과 중복은 줄고, 사각지대는 드러나며, 검증 가능한 중단 기준이 생깁니다.
아무것도 생산하지 않지만 이후 생산될 모든 것을 규율하는 문서는 어디에 배치해야 할까요? 흔히 쓰는 기준인 변화 속도만으로는 부족합니다. 그 자리를 기능 기준이 대신합니다. 이 파일은 결과를 생산하는가, 지식을 보존하는가, 상태를 기술하는가, 아니면 앞으로의 작업을 규율하는가. 아키텍처가 예상하지 못한 어떤 대상에도 쓸 수 있는 기준입니다.
몇 달 동안 만든 방법론이 이미 다른 이름으로 존재하는지 어떻게 알 수 있을까요? 방법은 몇 가지 동작으로 요약됩니다. 아이디어를 메커니즘으로 분해하고, 어휘가 아니라 기능을 찾고, 자기 분야와 영어권을 벗어나고, 새로운 발견이 무엇을 바꿔야 의미가 있는지 미리 정해 두는 것입니다.
AI로 빠르게 생산하다 보면 생각하는 시간이 밀려납니다. 이 시간을 지키는 구체적인 장치가 있습니다. 제한된 기둥 카드의 핵심 묶음을 간격 반복으로 살려 두고, 테이블 위에 펼쳐 새 생각을 자신의 신념에 맞세워 봅니다. 카드에 들일 기준, 복습 주기, 그리고 시작하는 방법까지 정리합니다.
어딘가에 켜 둔 Mac 없이 Contexte로 일하는 방법입니다. 구성은 세 가지 요소로 충분합니다. ChatGPT가 추론하고, 프로젝트 지침이 엔진을 정의하고, Google Sheets가 기억합니다. 실제로 전시회장에서 걸으며 대화 내용을 받아쓰고, 보존하고, 인제스트한 다음, 자리를 뜨기 전에 아직 던지지 않은 질문이 무엇인지 시스템에 물어볼 수 있습니다.
한 대기업 고객이 데이터를 자사 Azure에, 인증은 자사 IAM으로, 키와 LLM 계약도 자사 것으로 쓰고 싶다며 계약을 멈춥니다. 이 글은 그런 요청을 가려내는 기준을 제시합니다. 무엇이 실제로 우리의 가치를 담고 있는지, 무엇이 그 가치를 살 수 있게 만들 뿐인지, 그리고 고객의 통제권과 제품을 진화시키는 우리의 능력 사이에 경계를 어디에 그어야 하는지입니다.
Five days later, you rarely find the one paragraph that mattered in a long ChatGPT conversation. This is the story of how I got a precise fragment out of the flow on demand, using nothing but a custom instruction and a Google Sheets outbox — a blocked API, a workaround that failed, then a solution that went from 50 seconds to two, with a systematic check after every write.
Your best article ideas die between the moment they turn up and the moment you sit down to write. Here is the setup that catches them while they are still warm: the voice to empty your head without putting anything in order, a session source to keep the raw material raw, AI to surface the gaps in ten seconds rather than in two days.
Every new format feels like starting over: you reopen the last document, copy, rephrase, and two versions slowly drift apart. The cause isn't a missing tool, it's treating a deliverable as your source of truth. How to install a reusable layer between your sources and your documents, and what AI gains from it.
You can feel that a piece of writing or a decision isn't right yet, without being able to say why. That's where AI earns its place: it turns a vague unease into concrete handles — a blind spot, a shaky assumption, an objection you never dealt with. Which questions get you pushback rather than output, and why this makes human judgement more important, not less.
Your team rebuilds the same product model for every question, every bug, every tender. Here is how to write it down once: several dozen objects, a few hundred rules, under six hours. And above all how to know you have finished — the three stopping criteria that look like proof of completeness and prove nothing, plus the one that holds.
Hiring a PO to hold the backlog and sit between the business and the developers? You are optimising a circuit that is already obsolete. This piece takes apart the split between the people who do the thinking about the product and the people who execute it: why it degrades quality, why a backlog cannot support a profession, and why AI removes the last excuse for living with it.
AI raises the capacity to build, not the capacity to decide. Developers move up towards product; PMs move down towards building. The shift blurs roles without dissolving responsibilities. A full pass over what AI makes ordinary in product management, what stays hard, and a catalogue of emerging roles with the real risk attached to each.
Four days building a real product with Claude Code — 180 commits, starting from nothing. What it shows: the speed that goes to your head, the traps the AI creates on its own, what tests change when you haven't written the code yourself, and how far a PM can go without stepping outside their remit. A field report, not a doctrine.
Producing code faster is worth nothing if nobody understands what got built. AI automates precisely the tasks that used to train junior developers, and an error that lands too late no longer teaches anything once the system has grown too big to analyse. A few concrete anchors for staying in control: clear contracts between APIs, tests tied to the functional need, rebuildability as a quality bar rather than raw delivery speed.
Your documents never say everything. The fine-grained understanding of what happens on the ground stays in the PM's head. Session sources open a channel for pouring that informal knowledge into an AI Context — a hallway remark, a nuance picked up from a customer, a tension just starting to show — and turn dozens of micro-signals into notes, assumptions and better-framed decisions.
Your tools file information away neatly, but they never build up what that information teaches you. This piece explains why the future of the information system is not a better AI-assisted form, but a shift towards `Contexts`: portable, governed units of memory that connect sources, decisions and reasoning instead of merely storing them.
Do you lose half an hour in a test environment just to answer a product question on Slack? That hidden cost disappears once AI can query the source code, the real truth about how the product behaves. Answers grounded in evidence — functions, tests, commits — rather than in documentation that has fallen behind. Provided the code speaks the language of the business.
Do you lose the thread the moment you reopen a conversation with an AI about something that has been running for weeks? This article lifts the lid on a structured memory system: the difference between the goal and the attention of the moment, the directives, the offline queue, the three memories (log, synthesis, checkpoints) and the cycle of a session. Enough to see how an AI can genuinely remember a mission.
You think a market opens up once your product is translated? Brazil says otherwise. Through the most mundane scene there is — paying at the till — you'll see why everyday credit, a tax ID number, Pix and a visible informal economy form a cultural infrastructure no translation reproduces. Enough to avoid an expensive strategic mistake abroad.
An excellent note base isn't enough if the ideas never get absorbed. A flash card isn't a small atomic note: it's a personal pillar of thought, recognised in the heat of the moment by its resonance, tested over time by experience and by new sources. Rare by definition, it holds up what you really want to carry in you.
We pile up tabs, links and quick notes — and never read them again. The problem isn't the amount of information, it's that nothing is ever decided about what it becomes. This article separates capturing from building capital, and offers a simple rhythm for turning your captures into knowledge without drowning in them.
The same words travel between product, marketing, sales and leadership, and nobody gives them quite the same meaning. A glossary isn't a collection of textbook definitions: it's a tool for collective precision. It pins down the terms that carry decisions, protects the links between notes, and cuts the cost of conversations where everyone defends a different idea with the same vocabulary.
"One idea per note" is the formula everyone knows, and it sends most people in the wrong direction. An atomic note is not a short note. It is a note with a single conceptual centre of gravity. Once you see that difference, it changes how you capture, rephrase, title and link. And in the end, how you write.
A thematic note is the link between a note system and writing. It doesn't pile up everything that touches a subject — it picks an angle and brings several atomic notes together to make a pattern, a tension or a line of argument visible. Not a folder, not an encyclopedia: a temporarily stable view onto a network of thought.
Most organisations know how to produce documents. They don't know how to bank the reasoning behind them. On every decision they start again almost from scratch. The PM as Context architect turns scattered customer knowledge — transcripts, objections, past calls, weak signals — into a reusable asset. The result: faster, sturdier decisions, and an advantage competitors cannot copy overnight.
A zero-bug policy shrinks the stock of known defects. But if the team fixes them faster without changing how it builds, it stays stuck in a repair loop. The real issue lies upstream: giving ownership to those who ship, refusing overly vague specs, testing earlier, giving QA a quality-policy role rather than a catch-up one. Quality can't be delegated after the fact — it belongs to those who ship.
In many organizations, the backlog has become a clean trash can: you throw everything in so you don't forget. A few months later, 500 lines nobody understands anymore. A backlog shouldn't be a repository of ideas, a database of customer signals, or the graveyard of untriaged bugs. It exists to organize information mature enough for several people to work on it together. It comes into play when the work stops being individual.
Certain product decisions come up everywhere: in roadmap reviews, with sales, in specs, with every big client. Without a record, the company keeps re-deciding them, often with less context. The PDR — inspired by technical ADRs — documents these cross-cutting decision rules. Rare, short, immutable: it doesn't say what to build, it says why the company chose a rule. It removes dozens of pointless discussions.
A product team can pile up studies, workshops, and analyses without the company ever knowing what's a priority. The NNL roadmap answers this problem: not by scheduling dates, but by making commitments, serious directions, and possibilities visible — and above all, what won't be done. Its strength lies in the capacity constraint and in the implicit No.
The real problem with bugs isn't that they exist, it's the organization that grows used to keeping them. We prioritize them, we push them back, we review them in committees — until a customer crisis hits. A zero-bug policy aims at something else: zero known bugs left undecided. Either we fix it, or we accept it isn't a defect. What this approach refuses is the third state: knowing a bug exists and keeping it alive in a list for later.
Your teams leave the meeting aligned—and each walks away with a different version of the decision. The problem isn't a lack of meetings, it's the absence of shared objects. Glossary, one-pager, PR/FAQ, ranked metrics, decision log, escalation rules: these tools don't produce alignment, they force disagreements to become visible before they turn costly.
You leave a meeting with an action plan, yet nothing has truly been settled. This is what I call a soft decision: a non-decision dressed up as consensus. Organizations often prefer it to a genuine judgment call because it preserves the appearance of agreement without making the loss visible. This piece explores why the mechanism is rational in the short term, and why it costs so much at the execution stage.
Watching what competitors ship means reading outputs without understanding the reasoning behind them. Useful intelligence starts from the target customer: their needs, their decision criteria, their alternatives. Competitors only become interesting because they reveal how a market responds to those needs. Copying a move without understanding the logic behind it means reproducing an answer without ever having asked the right question.
Classic RAG starts from scratch with every question. By building an AI Wiki — a persistent wiki maintained by an LLM — you capitalize on domain knowledge once and for all. Atomic notes, links between concepts, contradiction detection: knowledge is compiled, not rediscovered. Lessons learned from 950 notes extracted from industrial maintenance sources, with calibration insights and concrete use cases.
Managing product opportunities inside a borderless network of notes means losing control: errors propagate silently, the AI context window blows up, and contradictions and decisions become impossible to find. The bounded context — borrowed from DDD — offers a better approach: each opportunity in its own bounded, auditable space, with a structured memory.
Drowning in email and losing track of the threads in flight? By handing the structuring over to Claude — one file, a few directives, then a gradual split — I turned 500 building-management emails into a queryable knowledge base. Seven steps, from the vague directive to a multi-file system, without ever needing a complex framework.
Documentation never keeps up with the code. We know it, we accept it, and yet it costs us time with every change. AI shifts the equation: when the code is clean, it becomes the source of truth from which the other artifacts—specs, changelogs, support documentation—can be regenerated. This code-centric approach demands a minimum of technical literacy, but it opens a real lever for the product managers who master it.
Too many insight systems fail because they classify everything along a single axis: features, or business stakes. Tactical feedback gets lost, strategic signals evaporate. A 4-level framework — business stake, use case, product capability, local friction point — lets you capture everything without a Rube Goldberg machine, and ties each signal to the right level of decision.
A wasteful skill locks you out after 3-4 runs instead of 8-10. Discover the 5 silent traps that saturate your quota, how to audit in 3 simple phases, and how to gain 40% more capacity without changing your model. Productivity regained.
Your days as a PM are devoured by tasks that have nothing strategic about them. In eight days on Claude Code, I automated my competitive intelligence — gathering, organizing, updating. Time reclaimed to analyze, understand, decide. This field report shows concretely why the center of gravity of the Product Manager job is shifting: fewer intermediate artifacts, more real strategy.
Producing software is no longer rare. The cloud commoditized it, and AI will accelerate the trend further. When everyone can build fast and well, churning out features by the yard is no longer enough. The real competitive edge shifts toward understanding the context: the business, the users, the customers, the competition, the standards. Understanding better than others, before building.
No more re-explaining the context at every session. Claude automatically retains what you did, the decisions made, the problems encountered — per project, inside your git repo, with no database. Portable, versionable, under $1/month. Here's how to set this system up in less than an hour.