Front End Development Communication & Stakeholder Relations 5 — Questions and Answers
Question 1: A marketing team wants to change the homepage hero image one day before a major launch. How should the front-end developer handle this?
- Assess the actual effort, communicate the risk to the launch timeline, and let the stakeholder make an informed decision (Correct answer)
- Make the change immediately without assessing impact
- Refuse all last-minute changes categorically
- Tell them to submit a ticket for the next quarter
Correct answer: Assess the actual effort, communicate the risk to the launch timeline, and let the stakeholder make an informed decision
Giving stakeholders accurate effort and risk information empowers them to make the final call rather than leaving the developer as the decision-maker.
Question 2: Which practice most effectively helps remote front-end teams stay aligned on UI standards over time?
- Maintaining a living style guide with contribution guidelines accessible to all team members (Correct answer)
- Holding daily three-hour design reviews
- Relying on each developer's judgment independently
- Restricting UI decisions to one designated developer
Correct answer: Maintaining a living style guide with contribution guidelines accessible to all team members
A living, accessible style guide creates a single source of truth that scales with the team without requiring constant synchronous meetings.
Question 3: A client provides contradictory requirements in different emails. What should the front-end developer do?
- Compile the contradictions, present them to the client, and request a single written clarification (Correct answer)
- Choose whichever requirement seems easier to implement
- Implement both versions and ask the client to pick at launch
- Ignore both and use their own judgment
Correct answer: Compile the contradictions, present them to the client, and request a single written clarification
Surfacing contradictions explicitly prevents wasted work and creates a documented resolution the team can reference throughout the project.
Question 4: What is the most effective way to demonstrate the value of front-end performance improvements to a non-technical stakeholder?
- Show before/after page load times alongside conversion rate or bounce rate data tied to business outcomes (Correct answer)
- Share Lighthouse scores and explain each metric in technical detail
- Send them a link to a performance blog post
- Describe the code refactoring that was performed
Correct answer: Show before/after page load times alongside conversion rate or bounce rate data tied to business outcomes
Linking performance metrics to business outcomes like conversion rates frames technical wins in terms stakeholders directly care about.
Question 5: A junior developer on the team is producing code that doesn't match the agreed style guide. The best first step is to:
- Have a private, constructive conversation referencing the style guide and offer to pair program on the next task (Correct answer)
- Post a public critique in the team channel
- Fix their code silently without informing them
- Escalate to a manager immediately
Correct answer: Have a private, constructive conversation referencing the style guide and offer to pair program on the next task
Private, constructive feedback with mentorship fosters growth and maintains team cohesion without creating public embarrassment.
Question 6: When writing a technical specification document for a new front-end feature, what audience should primarily drive its level of detail?
- The people who will build, review, and test the feature (Correct answer)
- The CEO who signs off on the roadmap
- External users reading release notes
- The marketing team writing launch copy
Correct answer: The people who will build, review, and test the feature
Specs are working documents for implementers and reviewers, so their detail level should serve those who need to act on them.
Question 7: A stakeholder says 'I'll know it when I see it' instead of providing clear UI requirements. The best technique to move forward is:
- Show multiple lo-fi wireframe options to converge on preferences quickly through visual comparison (Correct answer)
- Begin coding immediately and iterate until they approve
- Cancel the project due to unclear requirements
- Ask them to write a formal specification first
Correct answer: Show multiple lo-fi wireframe options to converge on preferences quickly through visual comparison
Concrete visual options help stakeholders who struggle to articulate preferences translate gut feelings into actionable decisions faster than written requirements.
Front End Development Communication & Stakeholder Relations 5
A marketing team wants to change the homepage hero image one day before a major launch.
How should the front-end developer handle this?