Panorama

Just watched my cofounder @haojingwei meditate on stage at a16z speedrun progress day!

It was honestly such joy working with @haojingwei on their @withpanorama new website. After first generic AI-style iteration, she told me to go "as bold as you can" and those words re-ignited my passion for unique sites with a character. I missed this feeling of a "flow"

kath is the name of one of our agents, it takes on user interactions. in sanskrit, kath is a verbal root meaning "to tell," "relate," "narrate," or "converse" guess the name of the agent who "does the work"

One question I get frequently when I talk about @withpanorama is: What metrics are important for a team's day to day operation? Before I wondered outside of my own neighborhood of engineering, the first thing came to my mind was "how many thank you or more accurately, signs of help provided, a team or person received per day, week or quarter": - I used to work on infra teams for years, IMO one important aspect of an infra eng's work is to unblock others (provide help & gather feedback from interactions). Infra is also a place where engineers get to build fancy stuff, and it's *really* fun to build fancy stuff, but that's a different story. - I've been talking to people: big tech, startups at different stages, engineers, head of eng, CTO, HR, design, research, exceptional recruiting lead, many founders at various stages of their journey. What I learned is the practical knowledge of something I intellectually know from reading psychology books: every team/group is at its own stage (dynamics), and for each set of dynamics, there are a set of metrics that'd make sense for that particular stage and for that group of people: I talked with a first time founder without prior management experience and just started off in engineering, the team is full remote, and from a different culture, the metrics for the team to focus in order to get to the next level of operations, will be very different from a team of senior engineers who worked together for 2 years or 3 companies together. And the moment the team gets to the next level of operation, the metrics for the team to focus on will need to be reset/re-evaluated.

panorama = the idea of observability (in engineering) applied to team operations

what a day in the life of a designer founder looks like. want a summary like this for your team? check out view.withpanorama.com

but ... dolphins are smart source: view.withpanorama.com

@harjtaggar 💯 we're trying to solve this — @withpanorama