Past Decisions Live in Someone's Head, Nowhere Else

“Yeah, that’s exactly the problem I’m trying to avoid. The idea is to keep the requirement, review history, who’s responsible for the next step, and the linked schedule activity together. But if keeping it updated takes just as much work as the spreadsheet and schedule, I haven’t solved much. In your experience, does tracking fall behind because updating it takes too long, or because nobody clearly owns it once comments come back? [re: Civil/land-development PMs: looking for feedback on a tool I’”

“What you describe sounds exactly like the classic Big Tech "rest and vest" trap, but it's worse because you actually want to work. The design friction thing is just what happens when designers become pixel pushers, they stop being partners and start being a bottleneck. On the engineering side, shipping the feature yourself probably made them look bad, so don't expect them to thank you for it. The uncredited side work is the real red flag. Your manager knows you're doing it,”

“Makes sense. If handovers are rare, a quick check of the main stuff in the live app is plenty. Thanks for walking me through it. [re: Have you tried giving your AI tools a memory of your project? What made you keep it or drop it?]”

“that seat invite stat is wild, 3x just from having conversation in the same view instead of email chains. construction crews already work in such a scattered way, half the crew don't even check emails regular i think it's not a fluke, seen something similar with a different tool where the chat itself became the onboarding because foremen would just @ someone and that person showed up next day with account already made. the PM features almost became secondary [re: one of our embed custome”

“It's all about context. When I first started doing this the PRDs weren't great, it made mistakes. No I've been working with Claude nearly a year, connected it to Jira, created templates, save most of my work to a second brain....it nails it first time pretty much every time. [re: Opinion]”

“This is true, after a while as a dev you need to understand the domain or how the system works (how data moves through the system) [re: I'm so fucking tired of corporate bullshit getting in the way of actual engineering]”

“reading through these, most of the fixes come back to the same thing, deciding something once instead of over and over. The shared doc for small calls, one list for feature requests, quietly dropping the spreadsheet nobody asked for. One more along those lines if you're small, give the stuff that drips in all day such as support emails, bug reports, admin bits one fixed slot instead of answering it as it lands. The work doesn't get any simpler, but you stop paying the context switching c”

“Every team has that one person who knows why the auth service retries 3 times, which config flag must never be touched on Fridays, and what was decided in that meeting nobody wrote down. That person gets interrupted all day. And when they're on vacation or leave, that knowledge goes with them. I got tired of being on both sides of that, so I built Cairn . How it works: You save small pieces of knowledge as you work: decisions, gotchas, preferences, context ("we use X instead of Y becaus”

“Every team has that one person who knows why the auth service retries 3 times, which config flag must never be touched on Fridays, and what was decided in that meeting nobody wrote down. That person gets interrupted all day. And when they're on vacation or leave, that knowledge goes with them. I got tired of being on both sides of that, so I built Cairn . How it works: You save small pieces of knowledge as you work: decisions, gotchas, preferences, context ("we use X instead of Y becaus”

“Another architecture review, another wall of diagrams and failure scenarios, someone saying "exactly-once semantics" like that ends the discussion. Nobody ever asks what happens when the feature flag service itself dies. Google's SRE book puts it at roughly 70% of outages coming from changes to a live system. Not the exotic failure modes in the diagrams. Someone flipping something in prod. I'm not saying feature flags are bad. I'm saying I don't trust anything with &quo”

“how does that plays out when it goes wrong though. If someone is clearly doing a ton of the coordination work (chasing alignment, unblocking other teams) but the shipped output ends up mediocre because of things outside their control, does the “helpful” reputation do anything for them at that point..? [re: Does the “behind the scenes” part of PM work count toward performance, or is it just assumed?]”

“But in the case you are blocked because you are coordinating and lets say Eng or Marketing takes forever to give you access to user data etc etc, this now turns into a bottleneck. Is it still my fault? who unblocks me? [re: Does the “behind the scenes” part of PM work count toward performance, or is it just assumed?]”

“Hi everyone, We’re currently building a demo for a hardware product, and I’m curious how other teams usually handle this process. We don’t have a highly experienced hardware engineer on our core team. Our usual approach is to discuss the product direction, concept, and main features internally, then pay external hardware and software engineers to build it. The process has involved much more back-and-forth than we expected. There are always details to clarify, decisions to revisit, and requiremen”

“The "not this" part gets skipped so often but it's the one that actually saves you from the endless back and forth after launch. seeing vague specs get treated like they're complete requirements is wild [re: The real reason "fast-moving" startups still ship slow (it's rarely the dev team)]”

“This is actually a useful idea. Rotating meeting times seems like such a simple fix, but i can imagine it making a big difference for teams spread across time zones. [re: Built a small Outlook tool to rotate recurring meeting times so the same global teammates don’t always get stuck with the late-night slot]”

“We had a working inventory management setup at my last company, built on Airtable. Did the job for about a year and a half. Our ops lead decided we needed "full control" because it was getting expensive, so we spent three months having a contractor build a custom version. Within six weeks of launch, the warehouse guys were back to texting stock counts to the ops lead because the tool double-counted returns and nobody trusted it. We quietly went back to a paid setup. Then this year, dif”

“Oh yeah, at least a year is best case scenario, but it seems maintainers rarely get that. I really think it was Manitoba that screwed things. [re: Google Workspace (GMail) doesn't understand the new BC time zone?]”

“a pattern that seems really common: alerts go to a slack channel and whoever sees it first deals with it. fine during the day, but at night nobody's watching the channel. so how do you handle it? rotation calendar? the service owner gets paged? and if the person doesn't pick up, does something escalate automatically or is it down to luck? pagerduty and opsgenie get mentioned a lot, but per-seat pricing adds up fast for a small team. grafana oncall comes up too. anyone running something h”

“I keep going back and forth on this. A lot of software today is basically a place where people type in what already happened somewhere else. Updating the CRM after the call, writing up the meeting notes, moving a task from the chat into the project tool. The software is useful, but someone has to feed it, and nobody creates value by feeding it. My guess is this category gets squeezed hard. If the information can be picked up from where the work actually happens (email, calls, chat), why would an”

“do you track win/loss on projects at all? like if a quoted project doesnt convert, having a "lost" status plus a one line reason field can be surprisingly useful when you look back at a quarter and realize half your leads dropped at the same stage [re: the 3 database client tracker i ended up with after overbuilding one (freelance setup)]”

“Good point - totally agreed on reliability and good communication.. what I noticed is , a client can give you a chance with one specific workflow then, if they like the performance, they can consider adding more .. [re: What do you look for in a BPO Partner?]”

“Throughout my career, I worked on several geographically dispersed teams spread across multiple continents. A recurring pattern I ran into was that regular team syncs almost always favored one primary office or time zone. As a result, the exact same folks in APAC or EMEA ended up taking calls at 6 AM or 11 PM week after week. Microsoft’s workplace research highlights that after-hours meetings have steadily climbed, and meeting fatigue is a massive drain on team morale when the inconvenience fall”

“Exactly. The texts and spreadsheets part is where it falls apart in practice. The job details end up scattered and nobody can tell what the latest version is. Once everyone is in one system the notes stay with the job and the office stops chasing updates all day. [re: The per seat pricing model punishes you for growing your team]”

“That's a really useful example because the breakdown wasn't necessarily in the workflow itself, but in making sure the handoff actually happened. Was billing getting delayed frequently enough that anyone tracked the financial impact, or was it just treated as another thing the PMO had to chase down? [re: At what point does PM accountability turn into being the human integration between systems?]”

“We have one communication channel: our ticketing system. If it's not in the ticket, it doesn't get actioned. This helps a ton. I also only take direction from specific people. Some random person wants something? It needs to come in writing from a designated resource. This creates a filter for disorganized clients and helps keep them on track. All of that structure helps a lot. If your client keeps changing their mind, you'll need to have a conversation with them, find out why, and la”

“The question already assumes simplifying worked. Where are the founders who cut a process and then watched something break for a quarter? They're usualy not the ones answering this. [re: What's one business process you wish you'd simplified earlier?]”

“The step I should have cut earlier wasn't the task itself, it was the wait for someone to approve it. I used to route every little change through the owner for a yes, and a quick fix would sit for days. Now we only require sign-off for things that affect money or customer commitments. Everything else gets a short window. If nobody objects by the end of the day, it moves. If you really need a second set of eyes, make the default approve rather than request, and have people flag only what they”

“Coming from backend, the jump for me wasn't a design course. It was refusing to ship a screen until it had an empty state, a loading state, and an error state. That's most of what makes a UI feel unfinished. After that, lock a spacing scale (4 / 8 / 12 / 16 / 24 / 32) and two type sizes into CSS variables and don't invent one-off pixels. A component library keeps the JSX consistent, but the scale is what stops your own layouts from drifting when the library doesn't have the piece”

“Honestly that might be the most accurate software engineering experience possible, especially the failing build part [re: "Take your child to work" day for remote workers. How?]”

“Thinking about architecture and scalability before writing code. As the CEO of an IT company, I’ve learned that the biggest waste of time isn’t development itself — it’s fixing poor decisions made early on. Good code solves today’s problems. Good architecture prevents tomorrow’s [re: What's a web development habit you wish you had built much earlier?]”

“How long have you had to fully on board onto this project? If it’s well documented you should see all the discovery, value props, and decisions made. If any of those are lacking, then best to form your own opinion based on discovery yourself. If it really has no value you better be sure of that before you tank this months long project. Go in curious and optimistic first- it’s easy to have doubt when you don’t have the full picture on a project mid flight. Take the time to really analyze, realign”

“A process map based on the CEO's understanding of how everything works... lmao [re: Building an interactive map of an entire company - every person, process and connection. Does this already exist?]”

“A firm I was working with on replacing part of their tech stack went radio silent after a few initial exchanges. I came to find out from my main point of contact that he decided to use Claude along with MCP connectors to extract data via the firm's existing disparate systems' APIs to create the reports and analyses leadership wanted, instead of looking to replacing the existing tech. As far as I know, he doesn't have agents executing actions in the systems. It's more like having”

“My "Dave" says, " I don't do documentation. If they know my processes, they'll get rid of me ". You are too right, Dave.. Too right. [re: twelve years in, three companies, and i keep finding the same guy]”

“This is still happening at random times across several organizations we manage. We have never found a solution. Does anyone have any updates on this? Moreover, I'm curious... does anyone with this issue use token protection CA policies? Wonder if that's to do with it. [re: Access Denied in New Outlook]”

“Start with the handoff, not the whole stack. You want one place where the client accepts the quote and that acceptance creates a job or to-do the crew actually sees. Keep Xero as the books and sync invoices from that tool instead of retyping. Add stock and ordering once the paper-to-screen loop is gone; bolting inventory on day one usually slows you down. [re: Software that moves accepted quotes into a to-do folder with notifications?]”

“I agree that for some tasks, splitting is worse than large PR. As I wrote in my response to u/Chris_Codes , the more important criteria is, that the PR accomplishes a meaningful unit of work. My 500 LoC boundary is a guideline / ideal size. Not a hard limit. The question is, whether 1000+ LoC PR remains the occasional exception or if it becomes the new norm. I feel that developers can't usefully review multiple 1000+ LoC PR's per day. It leads to review fatigue. [re: What does a normal s”

“It makes on-call hell. Because everyone's experience is forgotten. It's so easy now, especially if you use a single Claude session for debugging/researching, you can just ask it to summarize for you to copy and paste into whatever you use to document. [re: How do I deal with teams that don't document their work?]”

“the last minute thing they mentioned in passing that didn't seem important at the time but now is the entire reason they're calling [re: We built an app for the part before a client call: remembering where you left off]”

“The meeting is in your calendar. The last decision is in your notes. The update that changed it came in a message afterward. I'm on the team behind Ailoha!. We're working on that gap between having a record of a conversation and being ready for the next one. Say your notes show that a client is waiting for approval. A later message says the decision-maker has left. A useful catch-up needs both, because they change what you'd ask next. You share the relevant notes or screenshots with”

“I've spent some time working on documentation but I'm starting to notice that if you let colleagues expect that documentation covers everything you give yourself a lot more documentation work while they become more like to pass issues to you when they can't handle stuff beyond it with their skill and knowledge level. This is how I am and remain the one Powershell guy. Sometimes its just better to sit next to them to help them understand the technology they're actually working wit”

“The only way I ever found to debate priorities with executives is to lnow waaaay more than they do about how the product is used, and, to have some data about how many users have the same problems. If you don’t haventhe facts&data, an exec will assume their opinion is better than yours. [re: The problem with 2026 product management...]”

“If you can name your companies strategic goals, put your backlog in order relative to it. Then force whoever wants something to justify why it should knock something else off. Then document the audible and who made the call and replay it at the end of a quarter or whenever. You can't stop folks from demanding things but you can make priority clear and push back based on it. [re: The problem with 2026 product management...]”

Why On 13 October the fleet stopped twice while open issues remained. Every box found "No se issue is ready" and left, so nobody looked at why nothing was ready. Both times…

“I wouldn't trust the coordinator's memory past a couple of compactions. keep the plan and every task's state in a plain file it rereads each round, so compaction loses the chatter but never the ledger. [re: I got tired of juggling SSH and tmux across machines, so I built a terminal that makes them feel like one (open source)]”

“you can frame the speed and complexity as main points, like "led cross-team delivery of X features under tight regulatory deadlines" instead of user metrics, especially in b2b its impressive enough if you kept the wheels on while the client kept changing their mind [re: How would you package my experience in a CV?]”

“one thing that helped at my last company was refusing to start work until there was a clear problem statement, success metrics, and acceptance criteria. It forced better conversations upfront. [re: UX, Engineering, BA are covering for poor product requirements. How do we deal with this?]”

“My RevOps team spent mid-June to just before xmas last year on trialling and evaluating different AI tools across our SDR workflow. I wish I could say this was done in a super structured and organized way(!) but it was more like…sign up for a few that look good, run 'em for a few weeks then see what changes. Anyway, I thought I'd share my opwn experience to help anyone else looking to do the same because it's been a lot more effort than For context - we're a mid-market B2B team r”

“The biggest lever was a 5 minute working example, not docs. Developers try tools inside their existing workflow, so we stopped asking them to integrate and started giving them one copy paste command that solved a real pain in under 5 minutes. Trial starts jumped noticeably the week we shipped that. Onboarding calls are a tax you pay for a confusing first run. What does your first 5 minutes look like today? [re: How have you reduced the adoption cost of a developer tool? I will not promote]”

“One thing I would add to the process checklist: map out your file-locking and sync behavior BEFORE you start, not after. If any of your teams work on shared files (CAD, Excel workbooks, dev artifacts), the move from SMB shares to SharePoint/OneDrive sync changes the semantics — no more OS-level locking, version conflicts instead. The teams that migrate smoothly are the ones that inventory workloads in week one and decide which ones stay on a file server (or an overlay) instead of SharePoint. You”

The hours didn't change for me when the culture did. They changed when the dependencies moved. Half my engineering team is twelve hours out. Anything I didn't hand over cleanly by 6PM…

“"They have a really standard lifecycle: They get built. They work for a small department. If it stops there, it just keeps running until the person who built it moves on, then it gets trashed and replaced with something else. Or, if it grows beyond the department, that person's life starts to get taken up in maintaining it, it fails to scale, and IT takes it over (or replaces it)." This is how it was happening, its very different now and that's the reason why I'm asking this.Since you think I'm”

“What stands out is the eight years it took to understand something that others might overlook. Building software is one skill, but understanding an industry's problems deeply enough to make the right decisions is something different. The interesting part is that the work which once seemed less attractive turned out to carry the most value. That's a lesson earned through experience, not something easily replicated. [re: AI is eating our custom software work too. The one thing it has not t”

“Sounds like people dumping responsibility onto IT as usual. Your boss needs to get folks to answer your emails about call tree designs. You already did the technical work. And good job! Just a funny old YouTube video to help you feel better: https://youtu.be/uRGljemfwUE [re: Phone system nightmare]”

“starting from the thing that broke and walking back to the line beats pasting the console into a chat five times. making the agent wait for an ok before it edits anything is a good call too. [re: built a debugger for people who vibe code and have no idea why their app broke]”

“Ask the question you have from the research you have done. Not the network is slow, fix it and for the love of god never ever say “did you do something to the network? “ we have a freaking status dashboard and if we did maintenance that will affect you. We tell you. I forgive users for this one but if a support tech asks me some variant I want to scream and so does everyone else I know in that position. Asking if someone has reported something , ok but oh yeah Jeff i just rebooted all the switch”

“If Margaret has worked here for a year and been shown how to do that and we have detailed documentation yet still asks every time she has to deploy a package than yes, something is wrong [re: What does a IT support person need to learn to become a good system administrator]”

“It's important to map out their workflow in advance of building anything. Sit with them for a few hours and have them walk through their process step by step. Map it live with Miro, Figma, or Product Pillars. [re: Spent 3 months building a dashboard for a client. Almost nobody opened it.]”

“The Discovery step at the beginning was skipped. This is where the UX Researcher sits down with the boots on the ground to understand the critical workflows. [re: Spent 3 months building a dashboard for a client. Almost nobody opened it.]”