◆ Acrobat · edit

Manage Review Feedback

The [product spec PDF] needs technical and UX review by [deadline=Friday]. Share the file with both reviewers, enable …

3heights
3tasks
See the prompt↓More edit workflows

The same job, four heights

do it · improve it · decide · become
AExecute — “help me do it”The [product spec PDF] needs technical and UX review by [deadline=Friday]. Share the file with…+
The [product spec PDF] needs technical and UX review by [deadline=Friday]. Share the file with both reviewers, enable commenting, and highlight the three sections where I expect the most feedback: API limits, error handling, and user flows.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed.
BImprove — “do it better”Engineering will nitpick API details and UX will flag flow problems; both delay if they see the…+
Engineering will nitpick API details and UX will flag flow problems; both delay if they see the whole 40-page doc. Prepare a review-friendly PDF that opens to a short executive summary, numbers the sections I want feedback on, and pre-populates comment tags for bug, question, or suggestion. Explain to each reviewer what kind of answer I need and by when so they don’t just mark everything as ‘looks fine.’
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed.
CDecide — “help me choose”The product spec is due for launch and UX gave light feedback while engineering hasn’t…+
The product spec is due for launch and UX gave light feedback while engineering hasn’t responded. I’m unsure whether this is neglect, a sign they’re overloaded, or that they’re silently OK with the content. Diagnose which is most likely based on the limited responses, tell me what targeted follow-up to send to engineering that makes it simple to reply, and recommend whether to extend the review window or proceed with the current plan. Keep the follow-up warm, concise, and easy to action.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed.

The real tasks

1 of them
I circulated the spec and got only a few high-level comments from UX but none from engineering; launch is two weeks away.

Questions people ask

honest answers

Because you rarely think 'I want the redaction tool'. You think 'I have to share this without leaking the client's details'. Start from the need, and the feature finds you.

Real. Every job here was drawn from what people in real roles were actually seen doing in Acrobat — not a feature checklist.

No. Each page gives you a ready prompt you can paste into an AI assistant, plus the plain steps to do it yourself. Start with either — the goal is the finished job, not the tool.