@ridd_design@davidhoang@inflight My product team is rethinking how we prototype instead of figma/v0. At this stage we’re experimenting with an internal prototyping layer using Claude Code and our production component library - closer to how our engineers actually build. Eager to hear what you’re seeing on BYOT
@Shpigford@browsercompany Completely agree, having really easily switchable spaces with different profiles has been a game changer. Obviously the tab management as well.
@jasonfried Makes sense. Is the idea that the "capacity" required to achieve that rotation is built into the way you think about what can be achieved in a single cycle by a team? Also, do you manage this work within Basecamp aswell?
@jasonfried I imagine an example would be critical bugs reported by customers that can't be planned for. In my experience - without the appropriate capacity for this somewhere in the company ranks, it becomes difficult to meet the commitments on the betting table due to changing priorities
@jasonfried When you say you create a new "project" in Basecamp once you've decided what will be worked on in a cycle, is that new project broken down per pitch or per team? (Eg would a small batch team have a project that may have 2-3 pitches attached)
@jasonfried How do you stop yourself from building up a "backlog" of work to be shaped in your card tables? I believe it's only natural for ideas to develop over time but sometimes fall off the company's priorities.
@jasonfried Sounds great! I’d love to just hear about real world examples of your betting table finding problems, building ideas and choosing which is the most important to do next. How these choices fit into your strategy would be interesting to hear as well.