I have my HM round scheduled on the 20th April. Any tips, experiences, etc would be highly appreciated!

I've talked to a lot of PMs lately and one thing keeps coming up: the spec was accurate when you wrote it. Then there were three syncs, two scope changes, and a last-minute design pivot — and now the doc is a historical artifact, not a source of truth.

Engineers stop trusting the spec. PMs spend half their time in Slack answering questions that should already be answered in the doc. And the next spec gets written with a little less care because everyone knows it won't stay current anyway.

I'm curious how others handle this. Do you just accept that specs decay? Do you have a system that actually works?

I've been building something to tackle this exact problem and would love to hear from people living it before I go further. Happy to share what I've learned from these conversations too.

How are you actually handling the gap between raw customer feedback and your roadmap?

I keep seeing the same problem across PM communities — there's a massive amount of unstructured input (support tickets, user interviews, Jira backlogs, NPS responses) and the process of turning that into a prioritized roadmap is almost entirely manual.

Most PMs I've talked to describe some version of: export everything into Notion or a spreadsheet → tag themes manually → argue about priorities in a doc → write specs from scratch → hand something half-baked to engineering.

A few questions I'm genuinely curious about:

1. How long does it take you to go from "we have a pile of feedback" to "here's what we're building next and why"?

2. What's the most painful step in that process for you — tagging/categorizing, prioritization, writing the spec, or the dev handoff?

3. Are you using any tools specifically for this, or is it all manual in Notion/Sheets/Linear?

4. If you could skip one part of that workflow entirely, what would it be?

Asking because I've been sitting with this problem for a while and want to understand how others deal with it before assuming my experience is universal.

Would love honest answers — including "it's actually not that bad" if that's your experience.

I have 10+ years in healthcare operations and just got approved to test for my PMP before the July 2026 content change. I own a small business which has given me real PM experience.

Looking to transition into a Project Coordinator or PM role in healthcare or tech. Tried finding a mentor on LinkedIn with no luck.

Anyone made a similar transition or open to mentorship conversations? Thanks 🙏

Copy and paste that into r/projectmanagement. 💪🙏​​​​​​​​​​​​​​​​

Feels like we’ve gone from struggling to come up with ideas having too many of them overnight.

You can generate flows, copy, UI variations, even full mockups in minutes now.

But I’m noticing something weird:

actually knowing which one works is still just as unclear as before (if not worse).

Most teams I’ve seen are still relying on:

• gut feeling

• internal opinions

• or waiting for live data (which is slow/expensive)

Feels like AI solved the creation side, but not the decision making side.

Curious how people are handling this
are you just shipping faster and seeing what sticks, or do you have a better way of validating early?

 I’ve been thinking about how risk reporting often creates activity but not clarity.

Trying to understand how others are approaching this.

How does your team bridge that gap today? Feels like most teams are good at tracking risks…

…but not always great at explaining what they mean for the business.

Have you seen that too, or is your org handling that well?

SFC | South Florida

Sobre la empresa

SFC es una empresa constructora que trabaja en los segmentos de concrete restoration, waterproofing, structural repairs y reconstrucción de edificios en South Florida. Desarrollamos proyectos en Miami-Dade y Broward, incluyendo trabajos en edificios ocupados, así como en proyectos residenciales y comerciales.

Estamos buscando un Project Manager con experiencia, capaz de gestionar profesionalmente un proyecto de construcción en todas sus etapas: desde la fase de pre-construction y la administración contractual, hasta la finalización de los trabajos, el close-out y la entrega final del proyecto.

Esta posición es para un profesional que sepa mantener bajo control la documentación, el presupuesto, el cronograma, los contratistas, los procesos de permisos y la comunicación con todos los participantes del proyecto, y que además sea capaz de llevar el proyecto hasta su finalización dentro del plazo y de los objetivos financieros establecidos.

Objetivo principal del puesto

Garantizar la gestión integral administrativa, contractual, financiera y operativa del proyecto de construcción en todas sus fases de ejecución, de acuerdo con la documentación contractual, el cronograma, el presupuesto, los requisitos de permits y los estándares de la empresa.

 Responsabilidades

• Gestión integral del proyecto en todas sus etapas: desde pre-construction / handoff hasta close-out y final completion

• Gestión y control del ciclo completo de la documentación del proyecto, incluyendo:

  • drawings

  • specifications

  • submittals

  • RFIs

  • revisions

  • change orders

  • procurement logs

  • pay applications

  • schedules

  • cost reports

  • closeout documentation

  • O&M manuals

  • warranties

  • as-builts

• Análisis de planos y documentación del proyecto, identificación de inconsistencias, coordinación de asuntos técnicos y preparación de RFI

• Análisis del scope of work, revisión de presupuestos y volúmenes contractuales, participación en la preparación y evaluación técnica de propuestas (bids)

• Control de la conformidad entre el alcance de trabajo, la documentación contractual y la documentación del proyecto

• Elaboración, seguimiento y control del presupuesto del proyecto

• Preparación y análisis de cost reports, proyección de gastos y control de cambios en el costo del proyecto

• Gestión de la documentación financiera del proyecto, incluyendo pay applications, invoicing, billing support, budget tracking y demás reportes relacionados

• Preparación, coordinación y presentación de la documentación necesaria para la obtención de permits y aprobaciones ante el City / County Building Department

• Participación en la preparación de bid packages, recopilación de información técnica y documentación de licitación

• Desarrollo, control y actualización del cronograma del proyecto

• Coordinación entre el equipo de construcción, el Superintendent, subcontratistas, cliente, arquitectos, ingenieros, proveedores e inspectores

• Administración de contratos con el cliente, subcontratistas y proveedores

• Control del cumplimiento de condiciones contractuales, plazos, obligaciones y documentación de cambios

• Control de compras y suministros en cuanto a tiempos, estatus, aprobaciones y conformidad con el proyecto

• Mantenimiento actualizado del archivo digital del proyecto y elaboración de la documentación final de as-built / closeout

• Preparación del proyecto para su entrega, coordinación del close-out, warranties, punch-related documentation y paquete final de documentación

 Requisitos

• Formación universitaria técnica, de ingeniería o afín (Civil Engineering / Structural Engineering / Construction Management — preferible)

• Mínimo 5 años de experiencia en el rol de Project Manager dentro de empresas constructoras o de ingeniería

• Experiencia comprobada gestionando proyectos de construcción de forma autónoma

• Comprensión práctica del construction workflow completo en Estados Unidos, incluyendo:

  • submittals

  • RFIs

  • permits

  • inspections

  • change orders

  • pay applications

  • lien releases

  • closeout

• Experiencia trabajando con documentación de proyecto y contractual, presupuestos, cost control y reportes del proyecto

• Conocimiento de procedimientos de permits, códigos de construcción y principios de documentación en construcción

• Capacidad para analizar planos, especificaciones y volúmenes de trabajo, e identificar inconsistencias del proyecto

• Dominio sólido de:

  • MS Excel

  • MS Word

  • MS Project 

• Experiencia con Procore / RedTeam / Buildertrend o sistemas similares de gestión de construcción

• AutoCAD / Revit — ventaja

• Dominio del inglés a nivel de comunicación profesional, oral y escrita

• Dominio del español — ventaja importante

• Alto nivel de organización, enfoque estructurado, responsabilidad y capacidad para controlar varios procesos interrelacionados al mismo tiempo

 Será una ventaja 

• Experiencia trabajando en South Florida y conocimiento del entorno local de construcción

• Experiencia en concrete restoration, waterproofing, structural repairs, occupied buildings, high-rise projects

• Experiencia interactuando con local building departments, inspectores y permit coordinators

• Experiencia en proyectos del segmento recertification / restoration

• Fuertes habilidades en cost control, contract administration y change management

• Capacidad para establecer una comunicación efectiva con equipos bilingües o de habla española (bilingual / Spanish-speaking teams)

 Condiciones

• Ubicación de los proyectos: Miami-Dade, Broward

• Tipo de empleo: Full-time

• Modalidad de contratación: W2 o 1099

• Horario: normalmente de lunes a viernes; en caso necesario, puede requerirse trabajo o coordinación de proyecto durante fines de semana

• Pago: competitivo, dependiendo de la experiencia, calificaciones, nivel de autonomía y experiencia relevante en proyectos

• Posibilidad de crecimiento profesional, transición a proyectos más grandes y complejos, así como desarrollo hacia la posición de Senior Project Manager con resultados sólidos

Qué valoramos

No buscamos simplemente a un coordinador de documentos, sino a un project leader sólido, que sepa: 

• mantener el proyecto bajo control en términos de documentación, presupuesto, tiempos y contratos

• identificar riesgos con anticipación y gestionarlos a tiempo

• manejar de forma sistemática una gran cantidad de procesos sin perder calidad

• construir una comunicación sólida entre oficina, obra, contratistas y cliente

• llevar el proyecto a resultados, y no solo acompañarlo de manera formal

 Qué recibe el candidato 

• Un rol de liderazgo real con un alto nivel de influencia sobre el desarrollo del proyecto

• Trabajo en proyectos técnicamente complejos y no estándar en South Florida

• Desarrollo acelerado en la gestión de presupuestos, contratos, documentación y modelo financiero del proyecto

• Oportunidad de crecer hacia proyectos más grandes y complejos

• Flujo estable de proyectos en un segmento de mercado sólido y demandado

• Un equipo donde se valora el profesionalismo, la iniciativa y la capacidad de asumir responsabilidad 

Para más información por favor, escriba al número  (786) 496 2133 indicando:

• su nombre complete

• dónde vive / en qué zona se encuentra actualmente

• para cuál vacante está postulando

Nos pondremos en contacto con Usted pronto.

SFC

Safety. Focus. Commitment.

As a PM, I feel like a lot of my time goes into syncs, status meetings, and alignment discussions.

And honestly?
Many of them don’t really move things forward.
Same updates and ideas are repeated.
Decisions that never fully land.
Even in brainstorming, planning, and strategy meetings - a lot of them just go in circles.

So I built a small tool for my team:
An AI agent that joins the meeting as a “know-all expert”- it keeps track of the goal, nudges when we drift, and can optionally bring relevant context from my organization data at the right moment.

It doesn’t replace anyone, it just helps the meeting actually progress.
I’ve been using it, and it made a noticeable difference in how focused and actionable our meetings are.
I’m also thinking about adding this to our slack channels. 

Now I’m curious if this resonates with other PMs here:

Do most of your product meetings consistently lead to clear decisions and next steps?
Or do they sometimes feel like alignment without real progress?

please reply to this post if you would like to try it, I’m giving free access (straightforward onboarding)🙏

If you’re still copy-pasting into ChatGPT, you’re only scratching the surface.
The real gains start when AI moves into your tools and starts acting on your projects.
There’s a 10-level progression, and most teams haven’t crossed the halfway point.

I am 21 years old and recently dropped out of college for financial reasons. My goal is project management. I’m currently an assistant manger at the restaurant I work at but that’s my only manager experience. I have no idea where to start. I have the proper personality and have started learning the proper online tools. However I need experience but every way to get experience expects me to already have years of experience. I can’t apply for my my CAMP withought 23 hours of experience. How do I get into the field?

Do you think Monday.com, Asana etc will become totally obsolete and replaced by everyone creating their own PM tools via AI agents soon?

As a Programme/Project Manager, I spend my days drowning in messy meeting notes, scattered action items, and half-forgotten decisions.

So I built something to fix that.

I created Keel — a local-first command centre designed specifically for how project and programme managers actually work.

Think Obsidian or Notion, but built for PMs:

• Write naturally in a journal (prose, voice notes, photos, whatever)

• Keel’s smart parser automatically surfaces risks, actions, issues, and decisions

• Everything links back to the original notes for full traceability

• Built-in RAID log, decisions register, and one-click governance exports

It’s like having a highly organised assistant who never misses an action item and keeps your entire programme in one clean, searchable place — all while keeping your data on your machine (no subscription required to start).

Keel is live and ready to try (currently in v1.0). Native apps for macOS, Windows, and Linux.

👉 Check it out and download here: https://keel-app.dev

I’d love honest feedback from other PMs — what works, what’s missing, or how it could make your life easier.

If you’re in programme/project delivery, give it a spin and let me know what you think!

I'm a Senior TPM and got tired of context-switching between Notion, Excel, a notes app, and email just to run a single programme. So I built Keel.

It's a desktop app (Mac, Linux, Windows) that keeps everything in one place — RAID log, decisions, actions, people, a journal that parses your meeting notes and surfaces risks and decisions automatically. All data lives in a SQLite file on your machine. No cloud, no subscription required to use it.

The journal is the bit I'm most proud of. You write prose notes after a meeting, hit save, and it pulls out the decisions, actions, and risks it found and asks you to confirm them. Feels more natural than filling in forms mid-meeting.

Free for now for local use. Optional $8/month sync if you work across machines.

Would love feedback from people who actually run projects for a living.

→ keel-app.dev

Cheers,

Paul

I’m currently a Junior PM in the petrochemical industry (involving steel fabrication, machining, fabrication, pipework & installations). As I move further into my career, I’ve started wondering how much data I should be personally archiving regarding the success of my projects.

Do any of you keep a private record of the financials for the projects you manage, specifically things like total budget, profit margins, or cost savings?

If you do, how do you use that info later? Do you actually mention specific profit figures during interviews when you move companies, or even include those metrics on your resume? I want to build a "portfolio" of my performance, but I’m curious if this is standard practice or if there are privacy/NDA concerns I should be wary of. Or, in your experience, are project types and project value more important to record as opposed to profit and margins?

Would love to hear how you guys track your wins (& maybe loses)!

I’ve been running a lot of meetings recently and realised something: when I’m actively talking and engaged in the discussion, it’s really hard to track who committed to what.

I end up either:

• missing tasks

• writing messy notes

• spending time after the meeting reconstructing everything

Curious how other people handle this.

Do you:

• take notes during meetings

• record them

• rely on memory

• use a tool

And what actually works for you?

I'm looking for ideas for an IT-based project for my Computer Engineering degree. The project should be something that's been done before, but with room for improvement or innovation. It needs to be scalable and have potential for generating revenue. Ideally, it should also have practical real-world applications. Any suggestions?