Customer Feedback Correlation · docu tools · Pin Placement Flow
What customers said,
what we already knew.
Five verbatim feedback items mapped against the Pin placement audit — confirming what we suspected, and revealing one pattern we hadn't named.
Four of five customers are asking for the same thing: less manual work to name and tag a Pin.
The audit framed this as scattered friction — recent titles here, categories there, no templates on Web. The customer voice consolidates it into one job-to-be-done: "stop making me type the same metadata over and over." Customers have already invented workarounds — template projects, manual report-time checks, after-the-fact renaming — which is the strongest possible signal that the gap is real, frequent, and painful.
Item-by-item analysis
Each piece of feedback, against the audit
For each item, the verbatim quote on the left, the analysis on the right. Highlighted phrases are the signal-rich fragments. Tags indicate whether the feedback confirms an audit finding, surfaces something new, or points to a regression.
Is it possible to preconfigure categories with regard to keywords and titles? For example: When I select the plumbing category, I would like the pin title to be automatically filled in (SAN Fotodoku) and the keyword (Fa. Liebelt). I realize these settings would have to be set beforehand in each project for each category. (...) I would like to assign datasets to the categories that are required for these. (...) My problem is that I always have to rename pins afterwards and insert the keywords.
What this confirms
Maps directly to the audit's R7 (extend pin templates & quick actions) and R1 (category-aware Pin entry points). The customer is essentially describing a category-driven template — exactly the iPad pattern (T1/T2/T3) the audit recommended generalising.
What this adds
The audit assumed templates live independently; this customer wants templates bound to category. That changes the data model — categories become the carrier for default title, keywords, and required datasets. Worth elevating in the design spec.
Workaround revealed
"I always have to rename pins afterwards" — confirms the audit's hypothesis that title-setting is a high-friction recurring action, not a one-time cost.
I would like to be able to assign categories to pin titles and keywords (...). On the construction site, we would then only have to create a pin with the corresponding category and add photos – all the information needed for reporting would then be automatically included. Currently, we have to regularly check the group function to see if new pins have been created so that we can edit them manually. Since several employees are working on the project at the same time, it often happens that reports are created without a pin title or keyword, which is not desirable for us internally. (...) Ideally, we could create the default settings in a template project (including pin categories and designs) and then copy this for new projects.
What this confirms
Same root cause as Item 01, independently voiced. Two customers asking for the same thing in different words is a much stronger signal than one asking twice.
What this adds — and it's significant
Three new dimensions the audit missed:
1. Multi-user reporting integrity. "Reports created without a pin title or keyword" is a data quality issue, not a UX issue. This elevates the problem from "annoying" to "breaks downstream reporting."
2. The Group function as a workaround. They use Groups to audit for missing metadata — completely outside the feature's intended purpose. Classic workaround fossil.
3. Project-level templates. Customers want to define the Pin setup once at a "template project" level and copy. This is bigger than Pins — it's a project-configuration feature with Pins as a primary use case.
Implication
This is the single highest-leverage piece of feedback in the set. It justifies a category-templates + project-templates workstream that would resolve four of the five items at once.
Is there a list of all the text suggestions I get when I enter a pin? I would like to edit this list — also delete suggested pin names — as these have not appeared throughout the project.
Direct answer to an open question
The audit's open question Q1 asked: "How do users currently use 'recent pin titles'? Is it rescue-after-typo, or a genuine shortcut?" This customer has answered it: they treat it as a curated list they expect to govern, not a transient suggestion. Today they can't, and that breaks the mental model.
What this adds
A specific design requirement: recent titles need a management view — list all, delete unwanted, ideally pin/promote favourites. This complements (doesn't replace) the category-template idea from Items 01–02. Recent titles are the ad-hoc list; templates are the governed list.
Strategic note
Confirms two layers of need: admin-curated defaults (Items 01, 02) for discipline, and user-editable recents (Item 03) for flexibility. Both should exist; they serve different jobs.
If you create a new pin and then take photos with the ShortCut photo, you have to enter a pin name afterwards. This wasn't the case until a few weeks ago and is super tedious! Where can I deactivate this?
What this confirms
The audit identified the iPad's "create pin and photo" quick action as the strongest pattern in the product. This customer is using it heavily — so heavily that a behaviour change broke their flow within weeks. Validates that quick actions are a core workflow, not a niche feature.
What this adds — urgent action
This is a regression, not a feature request. Something changed recently that made the photo-shortcut flow worse. Three immediate actions:
1. Engineering should hunt the change-set responsible.
2. Support should be checked for similar tickets — this customer is unlikely to be the only one.
3. The fix and the larger redesign (Items 01–02) should be coordinated, not parallel — fixing the regression with title-skip-by-default also previews the category-template behaviour customers are asking for.
Tone signal
"Super tedious" + "Where can I deactivate this?" — the customer is past polite. They want it gone. Treat as urgent.
If I place a pin directly on a text (e.g. room stamp) in the plan, it would be helpful if this text is automatically adopted as the pin title. In general, it would also be very practical to be able to mark and copy text passages in the plan — both on mobile devices and on the PC. This would significantly speed up and simplify the naming of pins.
What this confirms
Same root pain as Items 01, 02, 04 — title entry is friction. Different proposed solution.
What this adds
A smarter, context-aware pattern: infer the title from what the Pin is placed on. Technically heavier than category templates (requires plan-text recognition or selection), but conceptually elegant — the Pin already knows what it's near.
Strategic position
Treat as an adjacent capability, not a replacement for category templates. Category templates handle the "I know what I'm documenting" case; OCR-based titling handles the "let the plan tell me" case. Both reduce typing; both serve different mental models.
Caveat
The audit didn't test plans with text annotation, so feasibility depends on rendering layer. Worth a separate engineering spike before committing.
Correlation matrix
Where each item maps to existing findings
Cross-references each piece of feedback against the audit's themes, recommendations, and open research questions. ● direct match · ◐ partial overlap · — no link.
| Audit reference | FB 01 | FB 02 | FB 03 | FB 04 | FB 05 | Net signal |
|---|---|---|---|---|---|---|
|
T1 — Mobile has no "New Pin" entry
|
◐ | ◐ | — | ● | — | Indirectly reinforced — customers want fewer steps, not necessarily a new button |
|
T3 — Unnecessary confirm steps
|
● | ● | — | ● | ● | Promote to high. Customers feel every redundant step. |
|
T5 — Android drifting from iOS
|
— | — | — | — | — | Not reflected in this sample — likely because feedback skews toward power users on iOS/Web |
|
R1 — Persistent "New Pin" entry
|
◐ | ◐ | — | ● | — | Reinforced by the photo-shortcut regression |
|
R7 — Templates & quick actions
|
● | ● | ◐ | ● | ◐ | Strongest customer signal. Promote to top of roadmap. |
|
Q1 — How are recent titles used?
|
— | — | ● | — | — | Answered. Users want governance over the list, not just suggestions. |
|
Q2 — How many categories & how stable?
|
◐ | ◐ | — | — | — | Partial — customers reference category names, suggesting trade-specific stable sets. Worth confirming in interviews. |
|
Q3 — Dataset attachment frequency
|
● | — | — | — | — | Partially answered — datasets seen as category-bound, not free-floating |
What the audit didn't catch
Three new findings the customer voice surfaced
Where customer feedback genuinely added information beyond what the audit captured. These deserve to be folded into the next iteration of the audit document.
Project templates & project copying
Customers want to configure a "model project" once — categories, defaults, designs — and clone it. This is a project-configuration feature, not a Pin feature, but Pins are the primary use case. Worth a separate discovery thread that includes Sales (do prospects ask for this?) and CX (which power users already simulate it?).
Reporting integrity as a driver
One customer explicitly framed the missing-title problem as a data quality risk for reports, not a UX annoyance. This re-frames the value proposition: title automation isn't just convenience — it protects downstream deliverables. Strengthens the business case.
Context-aware titling from plan text
Auto-inferring the Pin title from text underneath it (room stamps, labels) wasn't on the audit's radar. Technically heavier than category templates, but conceptually distinct — solves a different mental model. Worth an engineering feasibility spike.
Recent regression in the photo shortcut
A customer reports the photo-shortcut flow got worse "in the last few weeks." This is a release regression, separate from the redesign. Needs immediate engineering hunt and a Support ticket cross-check before it appears in churn signal.
Priority shifts
What this changes about the roadmap
Customer voice doesn't just confirm — it re-weights. These are the priority changes the feedback justifies.
So what
Six things this changes about how we proceed
Direct implications for the next phase of work
- Lead the redesign with category templates. The customer voice has consolidated four scattered audit findings into one job-to-be-done. Make it the headline of the design proposal — "Pins that fill themselves in" — and structure the rest around it.
- Add a regression-fix work item this sprint. Item 04 is not a future feature — it's a customer in pain right now. Decoupling it from the redesign timeline shows responsiveness and removes a churn risk.
- Validate Theme 5 (Android parity) separately. This sample didn't surface Android complaints, which doesn't mean they don't exist — it means feedback-board posters skew to a particular profile. Pull Support ticket data by platform before deciding whether to re-weight.
- Treat project templates as a separate-but-adjacent initiative. It's bigger than Pins. Loop in a PM for that thread; don't bolt it onto the Pin redesign.
- Use Items 01 and 02 as the artefact when pitching the redesign internally. They are unprompted, specific, and emotional — far more persuasive than the audit's severity dots.
- Re-shape one interview question. In the CX interview guide, replace question C2.1 ("workarounds customers invent") with: "Have customers told you about pin-naming workarounds — template projects, manual report checks, after-the-fact renaming?" — to verify whether the patterns in this small sample generalise.