Skip to content

icon picker
PRD: BiG ES New Website

Figma's Product Requirements Doc template
Last edited 31 seconds ago by System Writer
New Website Design
Team: @Marketing @Product
To last version of BiG ES new website
@Not started
May 30, 2020

Problem Alignment

The Problem (e.g.)

Designing a bank web poses several challenges and opportunities. A bank website must provide customers with a user-friendly, secure, and reliable platform to perform their invest transactions, manage their accounts, and access a range of financial services. Additionally, the design should foster trust and credibility, which is essential our bank's identity and long-term success.
There are several insights to consider while designing BiG ES website, including:
User Experience: A good user experience is essential for a bank website. Users expect a simple, easy-to-navigate platform that allows them to complete tasks quickly and efficiently. Clear, concise, and well-organized information is crucial to ensure users understand the products and services offered by the bank.
Security: Security is of utmost importance when it comes to our bank website. Customers need to feel confident that their personal and financial information is safe from hackers, identity theft, and other cyber threats. A secure website with strong encryption and multi-factor authentication with an easy going access should be our main priority.
Branding and Trust: BiG ES website should be designed in a way that reflects his brand identity and values. The website should be professional, visually appealing, and instill trust in customers. Good branding will help customers associate positive experiences with the bank.
Accessibility: Accessibility is another crucial factor to consider while designing a bank website. The website should be accessible to all users, including those with disabilities. This includes using proper color contrasts, font sizes, and other design elements to ensure everyone can access and use the website.
Mobile Optimization: With our bussines model mobile optimization is critical. 64% of our new clients enters from the mobile. The website should be responsive, easily accessible, and functional across different mobile devices.
Continuously Monitor and Improve: Continuous monitoring and improvement are necessary to ensure that the website meets the evolving needs of users and the business. Regular usability testing, user feedback, and data analysis can help identify areas for improvement and inform future design decisions
The design of a bank web is essential for the success of the bank and the satisfaction of its customers. It can impact customer loyalty, brand image, and business growth. A well-designed bank website can provide users with a positive experience, simplify financial tasks, and promote trust and security.

High-level Approach

Describe briefly the approach you’re taking to solve this problem. This should be enough for the reader to imagine possible solution directions and get a very rough sense of the scope of this project. (e.g., if “The Problem” was engagement in the design process from non-designers, “The Approach” might be a feed which surfaces work that's relevant to them.)

Goals & Success

What does success look like? What metrics are you intending to move? Explain why these metrics are important if not obvious.

Solution Alignment

Key Features (e.g.)

There are several insights to consider while designing BiG ES website, including:
Account Management: Allow customers to view clear account balances, transaction history, and manage their accounts.
Funds Transfer: Allow customers to transfer funds between accounts and to other banks in a easier way.
Invest Planning Tools: Offer invest planning tools such as “Crea tu Cartera” and saving calculators.
Security Features: Incorporate strong security measures such as multi-factor authentication and encryption to protect customer data and prevent fraud. ? Patricia
Customer Support: Provide a more accesible customer support through various channels such as phone, email, and chat to assist with any questions or issues.
Alerts and Notifications: Enable customers to set up alerts and notifications for account activity, such as when a transaction is made or a payment is due
Personalization: Use customer data to personalize the user experience with VENTAS, such as offering relevant products and services based on their transaction history and browsing behavior.
Quick Apply: Enable customers to quickly apply for pre-approved investment products with minimal information required.

Key Flows

I believe it is essential to demonstrate the design process as it progresses. Through Figma, we can observe the website's development in real-time and gain a comprehensive understanding of its various components. This approach enables us to closely examine how the product functions and ensure that it meets our objectives
Embed example:
⭐️ In the future, we will provide here a link to access the new website

Open Issues & Key Decisions

Keep track of open issues / key decisions here. Sometimes, certain decisions are made that might feel controversial; document these here so people know that the discussions have happened and there’s strong awareness of the tradeoffs.

Launch Readiness

Key Milestones

Identify any relevant milestones (e.g., a Dogfood or Beta milestone) that people should know about. Make sure to show when you’re expecting to publicly launch, too.
Fri, Feb 24
Internal employees only
Testing internally
Sat, May 30
Beta 👥
Early cohort of 100 customers
Getting user feedback
Tue, Jun 2
Launch! 🚀
Gradual ramp over the day to 100% of all users
It's the big day!
There are no rows in this table

Launch Checklist

Make sure you answer all of the questions below and involve necessary stakeholders.
Instructions if "Yes” (or unsure)
Will new learning material be needed (or updates to existing documentation)? Help Center articles? Images/GIFs? YouTube videos? Plugin documentation?
Talk to the Product Education team.
Will this feature require new support processes, like saved replies, new tags to track feature changes, or training the support team on new products/changes?
Talk to the Support team.
Growth & Data
Have you implemented sufficient tracking in order to measure success, risks and impact on user behavior for the new feature?
Involve your data counterpart to make sure feature is well instrumented.
Could this impact Growth numbers? (E.g., impact to NUX, UI changes to CTAs.)
Let the Growth team know. Consider running this as an A/B if you haven’t already.
Are we turning this feature on for everyone immediately (versus a gradual rollout)
Defend in this section why you’re opting for an instant ramp to 100%.
Are we running a Beta for this?
Talk to the PMM team.
Do we need an onboarding experience?
Talk to the PMM team.
Will this be available only in certain tiers (Pro or Org)?
Make sure the Enterprise team is in the loop and have good reasoning for your packaging decisions. In addition, if this is to be included in sales enablement material, talk to your PMM.
Is this a new action that should be included in the Activity Logs?
Talk to the Enterprise team.
Are you introducing new functionality that we’d want to add to our Web or Plugin APIs?
The general expectation is that the feature team builds these capabilities into these APIs. Talk to the Platform team if you have questions.
Could this break any existing integrations (e.g., with Zeplin, JIRA)?
Talk to the Platform team.
Will this introduce new work on mobile or mobile web?
Talk to the Prototyping team.
Security & Privacy
Are you introducing new data models, or exposing new API end points? Or are you changing anything to do with Authentication, Sign in, or Sign up? Is data flowing to a new vendor or outside of Figma prod ?
Talk with the Security team.
Are we collecting any data that we did not already, or are we using any data in a manner that we did not already use it in?
Talk with the Legal team.

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
) instead.