So there is a task; it's yours. It's ill-defined; that's not your fault.
Your fault is presenting the seemingly irreconcilable, incomprehensible, incomplete or otherwise irrational requirements as a blocker the next day during our daily stand-up. And I'm not even talking about how this privileged time is for coordination, not for reporting—you're not in school any more.
In a few words, don't just wait around: address the problem. You were never brought here to carry on doing the dull thing you've come to expect of yourself: we have machines for that, infallible tools working around the clock and churning through any task (defined explicitly enough) faster than you can click "assign to me". You're supposedly here because we expect you to function autonomously, and possibly function despite the unexpected.
Who knows, with a bit of drive, you might yourself operate beyond
expectations!
Until then, heed these insights I want to share with you:
I know you've got a boss, a project manager, a scrum master, a team lead, a product owner and that there's also that one guy in the team who knows better that area and always takes it on, but I'll tell you here the reality: the one thing you have that you should cater to is your responsibility.
If you're lacking some resource, whatever it is, go acquire it.
The person that has what you need does have the 5 minutes to give it to you.
If you're worried they'd believe those precious minutes to be wasted on you,
chances are that you're pre-emptively making up obstacles to justify planned
mediocrity, but surely that
shouldn't serve as a respectable alternative to actually trying.
If your half-assed effort didn't pan out, try wholeheartedly.
Yes, you've left a comment on the Jira ticket and it's been
unanswered for a week; yes the guy's now on vacation; yes the
teacher's 12 minutes late... Do you suppose it's time to make like
a tree—we
can't run the risk of them showing up before the hallowed
15-minute mark? If they're not responsive enough in these
Escher-esque
Atlassian machinations, hop on Teams; if they're on vacation, and their team
doesn't know, and your team doesn't know... Just get started.
You were entrusted with this, you can use your better judgement to kick it
off in the right direction. Or switch things up, take this extra time and
opportunity to get familiar enough with the context to avoid over-engineering
it this once.
The mythical, elusive one person that may or may not hold the key isn't
that irreplaceable.
No, really, even if nobody else but "surely they" know, guess what: neither
do they. They're just in that position where they have to decide whether
something needs to be done, but there's not one person that knows anything.
Assuming your business makes money, it takes at least 4 people to know what to
do: the customer service front-line (or analytics squad), the marketing crew,
the legal department, and the developers in the trenches. Everybody in-between,
around and above is merely playing the "telephone game".
Think of it this way: if you can't get it from them, it's just as well as if
they didn't have it.
Who you gonna call? Nobody. Look at you, you're the captain now.
Or decide not to do it, but don't dwell on it, and don't tell me the next day that oops, you did it again.