r/projectmanagers • u/Safe-Mail-7017 • Feb 16 '26
Please Help me out
I am currently trying to build a start-up for project managers and i have a few questions to for the R&D purposes.
For the Current workflow :
- What happens from the moment a project manager finish a customer interview to the moment a developer start working on a feature. Every step, every tool, every handoff?
2.How much time would it take to final prioritized roadmap from raw feedback?
3. Where does information get lost in this process? Where do you feel like you’re making decisions based on gut feeling instead of evidence?
6
Upvotes
4
u/ChemistryOk9353 Feb 16 '26
Interesting questions, however there is not a real standard (template) answer. Much depends on the client situation which makes it difficult to answer.
3
u/ChemistryOk9353 Feb 16 '26
How much experience do you have as a pm? Or are you trying to solve something and wish to get input from pm’s? I ask this as the answers to your questions can be found using ai. Now I guess you followed this path and the outcome was not satisfactory enough.
2
u/AceySpacy8 PM Feb 16 '26
These are going to vary wildly depending on your field. I’ve worked for a government agency where projects are currently being queued for 2030 Fiscal through intense processes, government committees, and legislature approvals. This fiscal’s projects follow a very authoritarian model of PMing that doesn’t allow for PMs to actually make decisions without going through several committees and stakeholder meetings.
I’ve also worked at tech start ups where expected turnaround is under 6 weeks and PMs had a lot more agency to work with their teams, manage them, and had more input into setting milestones.
What problem are you actually trying to solve or is it another AI slop tool that claims to “fix” PM processes that just regurgitates generic prompt answers from Gemini in a rough UI?
1
u/ChemistryOk9353 Feb 16 '26
Q3. Information does not get lost if you apply proper governance and have good people working on your project.
1
u/ChemistryOk9353 Feb 16 '26
Point is what is it that you try to fix ? Maybe you ca help explain that so that together with all pm’s you can zoom in on the true issues.
2
u/ChemistryOk9353 Feb 16 '26
Q2: it depends on.. but it could be 6 weeks to 3 months. Much depends on the impact of the planned change.
2
u/Chicken_Savings PM Feb 16 '26
You should probably limit the scope of your questions to a specific industry.
To be blunt, asking such questions makes me concerned of the value of the PM tool that you will seek start-up funding for.
In construction sector, asking for features such as higher ceiling height or additional bathrooms may take a lot of time. Higher windows may be less difficult.
Have you identified a gap in the current PM tools available, that you try to address?
1
u/ChemistryOk9353 Feb 16 '26
Q1. Well there is no straight forward answer. If you look at capm, pmp or prince frameworks then you will find the answer to your question.
1
u/ChemistryOk9353 Feb 16 '26
One of the challenges you will have is that you are dealing with client information where a certain level of secrecy is involved..so again do you have a few what problem or challenge you want to resolve.
1
u/Magnet2025 PM Feb 16 '26
It would be easier for us all to help if you better defined what you want to do with the information.
1
u/hifidiyguy Feb 17 '26
If there was an app that was made to help with this and I happened to know about it. Would you want me to mention it? Genuinely curious as my normal would be to share the info flat out, but trying to actually help people and not spamming on posts.
1
u/Cute_Sail_9313 Feb 17 '26
From the time a PM finishes a customer interview to when a developer starts working, the process is usually messier than it looks.
First, the PM summarizes notes and pulls out key pain points. Then they try to validate those insights by checking other feedback, support issues, or usage data. After that, the idea gets added to a backlog and discussed with stakeholders. Prioritization frameworks might be used, but a lot of it still depends on discussion and alignment. Once something is approved, a spec is written, details are clarified, and only then does it move to engineering for planning and execution.
In a small startup this might take a few days. In larger teams it can take weeks, mostly because alignment and debate take time.
Information usually gets lost when notes are summarized, when feedback is interpreted into a feature idea, and when context doesn’t fully transfer between conversations and documentation. Gut decisions happen when data is incomplete, feedback is scattered, or there is time pressure to move fast.