information-management on S Anand

How the Innovation Team works

Sun, 03 May 2026 16:15:15 +0800

Based on 44 meeting recordings from February to late April 2026, here’s how Straive’s small team (3-6 people at any time, mostly freshers and interns) produce a continuous stream of client-facing demos across topics as diverse as image filtering, geospatial analysis, insurance contract verification, NFL medical scoring, OCR benchmarking, and song similarity clustering — often with a 24–48 hour turnaround from assignment to demo.

Here is how the team works:

Build demos, not products. Every task traces to a specific client meeting with a known date. “Done” means good enough to show once to one audience — not production-ready. The moment a demo works, it gets shown; refinement happens only if the client asks for more.
Show output first, always. Start every update by showing the thing — not explaining what you did to build it. If you don’t have output yet, say so in one sentence and then show where you are. Process is for after the food arrives.
One person holds all client context. The team lead attends client meetings, filters what matters, and translates it into specific buildable tasks. Team members build; they don’t need to know why. This keeps work relevant and prevents wasted effort on misaligned output.
Explore broadly, cut ruthlessly. Multiple tracks run simultaneously — robotics, embeddings, OCR, formal logic — but anything that doesn’t demo well gets dropped fast. The sequence is always: assign a loose exploration, see output quickly, deepen what works, kill what doesn’t.
Compress everything. Small files, single HTML pages, 50KB images, 30-line YAMLs. This isn’t aesthetic — demos need to load in bad hotel WiFi, repos need to clone in meetings, and files need to forward over email. Technical choices serve the demo context.
Make pipelines reproducible after they work. Once a demo runs, it needs shell scripts or CLI commands that reproduce it from scratch. No committed data, no manual steps, no “ask X how it works.” If someone can’t clone and run it, it doesn’t exist as an asset.
Operate AI agents, don’t just use them. The team’s primary skill is steering coding agents — Codex, Claude Code, Copilot — toward specific outputs under specific constraints. When stuck, push harder (“drive it to death”), switch agents, or change the prompt. Don’t wait for instruction on how to build something; use the agent to figure it out.
Numbers, not observations. Every story needs a specific number: 252 test cases passed, $22 for 2,300 slides, 40% cheaper per-deck vs. per-slide. Vague quality claims don’t survive a client meeting. If a finding can be quantified, quantify it; if it can’t, find a different finding.
Action over analysis. The output of every demo should answer “what do I do?” not “what do I know?” Sort students by who needs a call today, not by distress score distribution. Surface the critical failure in the warehouse footage, not a compliance percentage. The analysis can be one click away — it should never be the headline.

However, there are many improvements the team needs to make.

The Single Point of Failure Problem The entire team is dependent on Anand for direction, client context, task assignment, quality review, and stakeholder relationships.
Missing: Taxonomy and Discoverability of Demos The team produces dozens of demos, benchmarks, and data stories. There’s a vague mention of a “catalog” and a “demo list” that Anand maintains, but it’s personal and opaque.
Missing: Explicit Knowledge Transfer Between Members Team members work on parallel tracks with little cross-pollination. X’s work on 3D benchmarking uses similar methodology to Y’s UMAP work, but they don’t reference each other’s approaches. When Anand wants them to collaborate, he explicitly engineers it.
The Presentation Quality Gap Team members consistently make the same presentational errors across many months. Anand corrects these every time, but they recur because the corrections aren’t being internalized or documented.
Client Handoff Documentation Is Missing Several demos reach clients without clear documentation of what was built, what the inputs were, and how to reproduce or extend it. Straive’s pitch is “here is what AI can do for you” — but without handoff documentation, clients can’t do anything with the demo.
The Timing Problem on Model Choices The team regularly uses outdated or suboptimal models, then switches when Anand notices. The team doesn’t have a maintained “current best model for X task” reference. Each person relies on whatever they used last time or whatever they happen to know about.
The Right Senior Mentorship for the Right Stage Anand is simultaneously mentor, product manager, client liaison, and technical reviewer. This works but creates a bottleneck. More importantly, some of the most valuable mentorship happens late. The team would benefit from more structured “junior reviews senior’s plan before execution” moments — not Anand reviewing output after, but Anand reviewing the approach before.

Every point is spot on and totally useful to me. The best part is that it just required me to paste the transcripts and ask it to analyze the team’s structure.

You can analyze your own team meetings too. Paste a dozen transcripts into a good AI agent and ask it:

Based on these transcripts, what are my team’s principles and operating model? How should we improve and why? Share with specific examples from the transcript.

This is like hiring a $100/hr organizational consultant to attend your meetings and give you personalized feedback!

Advanced Google Reader

Sun, 16 Dec 2007 12:00:00 +0000

I’ve stopped visiting websites.

No, really. There’s only one website I visit these days. Google Reader.

Google Reader is a feed reader. If you want to just catch up on the new stuff on a site, you can add the site to Google Reader. Anything new that is published on the site appears in Google Reader. Right now, I’ve subscribed to over 50 feeds. There’s no way I can remember to visit 50 sites – so I’m actually able to read more and miss less.

In a sense, that’s the essence of using feeds to read stuff: remember less, read more and miss less. If I ever find an interesting site, I just add it to Google Reader and forget about it.

But it goes beyond that. You can subscribe to search results.

Videos, for examples. Subscribe to a search for google engedu on Google Video. Any new TechTalk at Google, you get it in your Reader. (The talks are fabulous by the way.) Or search for hindi movies.

Photos? Track new photos of the Indian cricket team on Flickr.

Movies? Get an update of the latest movie torrents from mininova or torrentspy. Or just get updates on American Gangster DVDRip.

Presentations? Track anything on Javascript or consulting from SlideShare.

Documents? Find new eBooks on Scribd.

Not all pages offer a feed. But Page2Rss offers a reasonable solution. It converts pretty much any page into a feed.

It’s gotten to the point where anything I know I want to read, I put it on Google Reader. The rest of the Internet is when I don’t know what I want to read.

Comments

Jayan 16 Dec 2007 12:00 pm: Same here. I ve been using it for over 2 months now. I subscribe to over 200 feeds. This reader is coool.. - (http://ekalayva.wordpress.com)
Simon32 16 Dec 2007 12:00 pm: I agree, RSS is great! Btw, you might also want to checkout Feedity - www.feedity.com for creating free custom RSS feeds.

Cut-and-paste is not understanding

Wed, 21 Jun 2006 12:00:00 +0000

Cut and paste has become easier. So we make less effort to understand. We don’t need to. Like when we pay less attention if we’re recording a lecture.

Solution? I suggest the Tunnel in the Sky strategy. Rod Walker is going for survival training on an alien planet, and asks his sister, Captain Walker…

“Uh, Sis, what sort of gun should I carry?”

“Huh? Why the deuce do you want a gun?”

“Why, for things I might run into of course.”

“Your only purpose is to stay alive. Not to be brave, not to fight. One time in a hundred a gun might save your life; the other ninety-nine it will tempt you into folly.”

“Did you take a gun on your solo test?”

“I did. And I lost it the first day. Which saved my life. I know how good a gun makes you feel. You’re ready for anything and hoping you’ll find it. Which is exactly what is dangerous about it - because you aren’t anything of that sort.”

So, don’t take a gun.

Don’t record lectures. Don’t give yourself the illusion of perfect memory.

Don’t bookmark for future reading. You won’t read it later.

Don’t cut and paste. You don’t understand it now. You won’t understand it later.

Comments

Sai 26 Jun 2006 11:36 pm: Good stuff..makes lots of sense…
Rajagopalan 26 Feb 2007 1:23 pm: that is why make sense software is becoming popular
Anonymous 15 Mar 2007 6:56 am: Brilliant :)

Social Bookmarking Tools

Mon, 18 Apr 2005 12:00:00 +0000

D-Lib magazine reviews Social Bookmarking Tools.

Comments

Jetru 18 Apr 2005 7:38 am: i think you forgot something:D

Professional news feeds

Thu, 05 Sep 2002 12:00:00 +0000

Professional news feeds. A treasure for RSS news junkies.

RSS newsreaders

Sat, 31 Aug 2002 12:00:00 +0000

Ever since I started using NewsIsFree.com, I manage to run through my morning news much faster. Now, I’m trying to use some of these RSS newsreaders to see if they can speed it up even further. (Note: Though I read news faster, I’ve ended up spending more time on it, not less!)

Subject specific scout reports

Sat, 19 May 2001 12:00:00 +0000

The subject-specific Scout reports, which were a prime source of my information, are about to be discontinued from the end of the month. (No funds.)