독서리서치레이더투자 프레임워크
로그인 / 회원가입
전체기술제품투자상장시장기타

독서

2026-11-077 게시물

새로고침

Colleen Aubrey, Head of Applied AI at AWS: Don't Invent New Metrics for AI, Measure It with Your Existing Business Metrics

주제 · AWS AI指标之争중대
2026-11-07 02:56 GMT+8

Colleen Aubrey has worked at Amazon for over twenty years, having built customer-facing products for millions of sellers and advertisers. In 2026, in her capacity as Senior Vice President of Applied AI Solutions at Amazon Web Services (AWS), she offered a rather direct suggestion for corporate AI practices: stop inventing new AI metrics.

Her core argument is that measuring whether AI is successful does not require a completely new system of metrics.

"I worry that people start trying to come up with new metrics to measure the impact of AI, but it’s the same metrics," she explained. "It’s your business metrics that matter."

This statement sounds simple, but it points to a widespread practical issue: after investing in AI, many companies build AI-specific dashboards for token consumption, prompt usage frequency, and model call tracking, only to find that while these numbers rise, business results remain stagnant.

The proof point Aubrey provides is Wells Vehicle Electronics. According to AWS reports, the company reduced inventory by 7% within three months while expanding the number of SKUs actively monitored from 20 to 2,000. She emphasized that no one at Wells talks about tokens; they talk about working capital. If a project cannot be tied to a metric the Chief Financial Officer is already tracking, it is an experiment, not an investment.

What does this distinction mean in practice? Aubrey suggests that before any AI project receives funding, bind it to a business metric the company is already tracking—inventory levels, problem resolution rates, hiring cycle time, production cycle time—and set a baseline. If this metric does not change within a defined time window, the project should not scale, regardless of how impressive the demonstration was.

Her argument also touches on a deeper mechanism: AI usually does not eliminate bottlenecks but moves them. Internal experience at Amazon shows that when AI coding tools were widely deployed, teams first discovered insufficient test coverage; after fixing tests, they found pipeline issues; after fixing pipelines, they found manual approval steps slowing down deployment. The result for Aubrey's team this year was a doubling of the rate of pushes to production, but she explicitly stated that this speed increase did not come from the coding assistant itself, but from fixing all the downstream problems exposed by the assistant.

The implication for enterprise procurement of AI tools is this: if you buy the tool but skip pipeline repair, activity will rise but output will remain flat. She recommends reserving budget and personnel for downstream fixes rather than discovering new constraints six months later.

Aubrey also proposed a lesson at the product strategy level: feature parity is a trap. When she took over the AWS supply chain product, the team was building five modules attempting to catch up with ERP vendors that had decades of head start. When she rebooted the product as Connect Decisions, she asked a different question: where is the pain most acute, and where are existing tools weakest? The answer was planners—who spend their days firefighting, overwhelmed by a flood of signals, by the time they make a decision the moment has passed. This principle of picking a wedge rather than a platform is what she sees as key to moving enterprise AI projects out of pilot mode. A narrow, painful problem yields quick wins, clear metrics, and a credible foundation for expansion. Projects that attempt to reimagine an entire function at once often stall.

출처:SiliconANGLE

리서치

German Police Use AI-Generated Image to Hunt Leipzig Drone Suspect

주제 · 莱比锡无人机袭击案간단한 요점
검증됨 2026-11-07 17:33 GMT+8

The German Federal Criminal Police Office (BKA) and the Federal Prosecutor's Office published an AI-generated image on Friday, November 6, to help identify a third suspect in the attempted drone attack at Leipzig Airport. The image depicts a slender person wearing a black hooded jacket and carrying a large backpack while riding an e-bike.

According to a report by Die Welt, investigators stated that the unidentified individual may have been near the airport between July 31 and August 4. Despite the summer heat, the person was unusually dressed for the season, wearing long sleeves, gloves, and a cap pulled low over their face. Two suspects have already been identified, and this composite image is intended to track down a potential third accomplice linked to the incident.

The attempted attack occurred on the evening of August 4 when an airport employee discovered a drone loaded with explosives on the ground near Ukrainian cargo planes. Leipzig Airport serves as a key hub for military aid deliveries to Ukraine. The German government previously blamed Russia for orchestrating the plot, which Moscow has denied.

출처:DIE WELT

리서치

Bosch Engineers Use Doubao Work Partner to Process Fault Reports: AI Draft Covers 70-80%, Value Lies in Post-Communication Rather Than Judgment Itself

주제 · 豆包工作伙伴企业应用중대
2026-11-07 11:35 GMT+8

R&D departments in automotive supply chain companies face a common dilemma: an engineer has to do the work of three people. They must monitor R&D details while also handling daily repetitive tasks. An engineer at a certain business unit of Bosch serves on a team that interfaces with various customers to provide comprehensive system solutions. For the same customer, different projects have different chat groups; if any issue arises during testing, road trials, or production, messages pop up one by one—specifying which project, which software, what fault code was reported, and what error occurred.

The engineer's previous workflow was as follows: gather messages scattered across various groups and private chats, integrate them into a complete description based on several dimensions such as project affiliation, software version, vehicle configuration, test conditions, error time, and diagnostic screenshots, and use experience to determine who to contact for troubleshooting. If explanations were unclear, meetings were held to clarify issues before issuing reports to customers. Half a day would pass before fault analysis even began.

Two things prompted him to make a change. First, knowledge accumulation is unreliable: experience resides in individual engineers' minds. While cloud documents and knowledge bases exist, everyone has different templates and habits, and when projects are busy, no one takes the time to input data. When personnel leave, experience is lost. Second, customers do not ask questions according to templates: problems occur in a streaming fashion, with messages constantly popping out. No one can provide fault codes, screenshots, and over a dozen fields all at once in a single message. If fragments cannot be collected completely, subsequent analysis remains stalled.

The addition of Doubao Work and Doubao Work Partner changed this path. The engineer configured scheduled tasks in Doubao Work to patrol private messages received, identify fault-related information, and forward it under their own identity to a dedicated topic group for problem reports. Customer communication habits did not need to change; matters scattered outside the process were pulled back into it. Once messages entered the dedicated group, each problem occupied an independent topic, naturally forming an interface for 'one matter, one discussion.'

Doubao Work Partner crawled historical context from the group, aggregated streaming fragments into complete problem descriptions, then called encapsulated report generation skills to produce drafts according to standard templates. Simultaneously, it registered entries in Feishu (Lark) Bitable, reminding the corresponding engineer to handle them. In one real problem-handling record, the AI organized messages into a Feishu document, marking the problem status as 'In Progress'; information such as drive form and driving mode, which was incomplete, was left as 'To Be Supplemented.' The engineer only needed to verify and fill in the draft, rather than starting from a blank document.

Some details could only be finalized during meetings. The engineer could invite Doubao Work Partner to attend problem communication meetings; it listened throughout and directly synchronized clarified information into the report after the meeting ended, eliminating the step of manual transcription between discussions, records, and reports. According to the engineer's own estimate, the AI draft could cover 70-80% of the content, leaving the remaining 20% for human judgment. After meeting conclusions supplemented the report, making it basically complete, it underwent one more round of manual review before being sent to the customer.

출처:GeekPark

리서치

Apple Announces Over 100,000 iPhone Duo-Optimized Apps as Major Software Follows Suit

주제 · iPhone Duo중대
2026-11-07 05:38 GMT+8

Apple announced on Friday that more than 100,000 apps optimized for its new foldable iPhone Duo are now live on the App Store, with thousands more being added daily. This milestone aims to counter early negative reviews citing a lack of native software support at launch.

The announcement coincides with the release of over a dozen notable Duo-ready apps, including Microsoft Word, Outlook, Zoom, sports apps from the NBA and NHL, shopping apps like Etsy, and productivity tools such as Goodnotes. These join previously available optimized apps like Netflix, YouTube, Instagram, and WhatsApp.

Non-optimized apps display a black bar on the side of the screen, wasting space and sometimes hiding key functions under overflow menus. Apple noted that over 2,000 developers attended more than 50 in-person workshops across 19 cities worldwide to help adapt their apps for the new form factor.

Despite a starting price of $1,999 for the 256GB model, the iPhone Duo sold out within hours of orders opening, with ship times shifting into next year. On its earnings call this week, Apple said it was "hard to predict" when supply constraints would improve. Susan Prescott, Apple’s vice president of Worldwide Developer Relations, stated, "It’s been wonderful to see how quickly developers have embraced iPhone Duo."

출처:TechCrunch

리서치

Figma CEO Dylan Field: AI Turns Code Production into the Floor, Design Judgment is the Ceiling

중대
2026-11-07 04:31 GMT+8

In a conversation with Ohalo Genetics CEO and All-In Podcast co-host David Friedberg, Figma CEO Dylan Field offered a perspective on competitive dynamics in the age of AI: "Design is the new code." His reasoning unfolds in two steps. First, AI is lowering the floor across all production stages—code, motion graphics, and video—making participation universal and democratizing production. Second, when code is no longer a scarce capability, it ceases to be a source of differentiation. What truly distinguishes products is the layer above code: design judgment and unique viewpoints.

Field acknowledges he once misjudged this landscape. He originally believed AI would raise the ceiling simultaneously—enabling humans to create greater works than before. But he states, "That was wrong." AI does not raise the ceiling; humans do. The ceiling is raised only when creators and designers choose to be bold, invest their time, and attempt things never done before.

This layered framework has practical implications. Field recommends a workflow where one first uses AI to generate a draft to overcome the blank canvas problem, then actively reacts to it by saying, "I don’t like these parts; I’m going to fix them." This approach is superior to asking AI to directly implement your vision, because doing so means thinking through AI’s perspective, ultimately yielding results that do not align with what you truly want.

Field further distinguishes between two paths: one where AI thinks for us, and another where AI expands our understanding of the world, enabling us to do things we previously dared not attempt due to difficulty. He explicitly chooses the latter: "Why would I want something else to think for me? My entire life has been dedicated to figuring out how to think."

The boundaries of this argument require attention. As the CEO of a design tool company, the statement "design is the new code" naturally serves Figma’s product narrative. Field provides no empirical data proving a causal link between design differentiation and market success, nor does he discuss whether design judgment itself might be gradually automated as AI becomes capable of generating both code and design. This is a strategic judgment from a tool manufacturer’s perspective, not a verified market discovery.

However, the value of this judgment lies in its ability to break down the vague question of "what will AI replace" into two actionable layers: lowering the floor means the entry barrier disappears, while raising the ceiling via humans means differentiation must stem from judgment rather than execution. For teams building products with AI, this distinction at least provides a clear starting point for thought—your competitiveness depends on whether you compete on the floor level or the ceiling level.

출처:Figma

리서치

Meta Executive Warns US Midterm Election Results Will Hinder Data Center Construction

주제 · Meta数据中心社区影响중대
2026-11-06 03:12 GMT+8

Meta President Dina Powell McCormick stated at the Wall Street Journal Tech Conference that Democratic victories in the midterm elections will make it significantly harder for companies to build data centers. She noted that the industry has failed to adequately explain the benefits of these investments, leading to increased community backlash against data centers. Powell McCormick emphasized that data centers, as the visible manifestation of AI technology, have become a focal point for public discontent, reflecting deeper issues regarding overall attitudes toward AI.

Meta currently operates data centers in 23 US states, with five projects—including one in Texas—planned to reach or exceed 1 gigawatt in scale. To mitigate local community resistance, Meta has implemented several measures, such as paying for its own electricity, directing tax surpluses generated by data centers toward teachers and first responders, keeping the labor force local, and securing bipartisan support. Powell McCormick argued that communities only accept data centers when projects clearly benefit them.

Despite political headwinds, Meta remains optimistic about its AI investments, particularly the growth potential of its consumer AI agent Muse. Even if AI applications do not achieve expected mass adoption, Meta believes the compute capacity itself holds value due to daily requests for leasing. This perspective indicates Meta's attempt to reverse negative sentiment by demonstrating technology democratization and tangible economic benefits, though the post-election political environment introduces new uncertainties for its expansion plans.

출처:TechCrunch

리서치

The Verge CEO Nilay Patel: AI Products Are Not Yet Good Enough to Justify the Costs Users Must Bear

중대
2026-11-07 01:13 GMT+8

Nilay Patel is the chief executive officer of technology media outlet The Verge. In The Vergecast podcast, he offered a judgment on the dilemma facing AI commercialization: the products are not good enough to justify the costs imposed on users. This is not an abstract market observation, but a specific causal chain—costs are real, benefits are not, and the disconnect between the two cannot be bridged by marketing.

Patel listed costs including data center noise encroaching on communities, AI overviews and deepfake content polluting the information environment, corporate spending exceeding revenue, and even European blood-storage refrigerators being hacked. His phrasing was direct: you cannot tell neighbors that they must endure the hum of a data center in their backyard for the sake of the most ridiculous AI slop content.

The issues on the benefit side are more subtle. Patel believes agents are not yet true agents, nor are they being used in the ways people expect. All companies are spending more than they are earning on these products. This means unit economics do not yet hold—not as an isolated issue for a single company, but as a structural state across the entire industry.

He linked this imposition of costs to political influence: CEOs shaking hands at the White House, renaming bodies of water, and paying for banquet halls they do not need, attempting to use political means to make users accept product costs they would otherwise reject. His judgment is that this is obvious crypto-corruption, and the products themselves remain slop.

Patel's prescription for the industry is a clear condition: the AI industry will not escape this predicament until they build better products—good enough that everyone can see, without needing to be convinced, without ad campaigns, and without any political maneuvering, that using these products improves their lives. This condition is important because it shifts the standard for industry recovery away from funding scale, compute investment, or political connections, and back to product experience itself.

It should be noted that Patel's assertion is an opinion rather than an analysis. He provided no specific quantitative data on costs versus benefits, nor did he discuss which product categories are approaching his standards. As a content media outlet, The Verge's business model is directly related to the quality of AI-generated content, giving his criticism of 'slop' a self-interested hue. However, his position as an external observer—who does not sell AI products and does not rely on AI revenue—means this judgment is at least free from the contamination of vendor self-interest narratives.

출처:Simon Willison’s Weblog

리서치

이 뷰에서 모든 콘텐츠를 확인했습니다

로그인 / 회원가입
독서리서치레이더투자 프레임워크

It must be noted that the data for Wells Vehicle Electronics comes from AWS's retelling and has not been independently verified. Aubrey's own narrative also indicates that actual productivity gains from AI at Amazon largely came from infrastructure repairs rather than AI tools themselves, making it complex to attribute results solely to AI investment as a single variable. Her advice serves better as an evaluation discipline—using existing metrics to verify whether a project actually changes business outcomes—rather than as causal proof.

Reports were simultaneously archived into the team knowledge base, with status and progress retained in Bitable: the table managed follow-up, while the knowledge base managed retention. When encountering similar problems again, the AI retrieved historical materials to provide initial ledgers and attributions. The knowledge it could call upon fell into two categories: one was external industry knowledge, such as the meanings represented by general fault codes; the other was the team's own historical accumulation, where even problems handled by veteran engineers who had already left could be retrieved and cited.

This project took just over a week from requirement to implementation. Doubao Work Partner truly went live in just one day; after joining the group and working alongside the engineer for a day, the project was already running. The following week was used to fine-tune details—which reports were too verbose, which content should not be included, which descriptions were inaccurate. The engineer could tell it item by item to avoid such processing next time. Currently, Doubao Work Partner has processed fifty to sixty problem reports and can stably maintain a level of 70-80 points. The remaining twenty points are left for humans to make the final checks: how to determine fault causes, how to arrange verification plans, and what conclusions to give externally. These key tasks still require manual review, supplementation, and confirmation by engineers.

The core judgment offered by this report is that the position where AI creates value is not the most central link in the workflow. By leaving communication, judgment, and the resolution of professional problems to humans, and handing over post-communication organization, recording, and action to AI as much as possible, engineers can free up their hands to do what truly requires engineers to do. AI does not necessarily have to do the most important things to create important value.

It needs to be pointed out that the core efficiency metrics are self-reported estimates by engineers, and overall data lacks independent verification; this process relies on the Feishu ecosystem and specific report templates, and the migration cost to other toolchains or more complex fault types has not been explained.