PayPal has Venmo integration coming later with Amazon. In my opinion it was announced way to early to be an event that could have been capitalized on. Also to think how many people will actually switch their payment method to Venmo when most people already have a funding instrument pre-selected. I imagine the number of peoples credit cards expiring this year to be a low number.
Also having said that, PayPal is not a company that will make Venmo with Amazon a value add for users. PayPal doesn’t innovate, they play catch up. The company knows that growth is not an option.
The only way to capitalize further is to increase transactions costs, integrate their non branded experience (Braintree) with more merchants, and seek out more deals/partnerships. Until then they’re gonna have to wait and see what will stick.
I would agree with you and say while there is no set advice or plan to follow (that would make things all too easy) there are a couple things here that we could all apply to our teams.
> Tracking automated test coverage (unit, integration, ui) is a performative task that doesn’t provide hard evidence to increase confidence with stakeholders. Instead we should shift automated testing from functional to compliant, accessible, and security based testing and track coverage there.
> Shift testing to the left. This has been a major problem in the organizations I’ve worked at and we should continue to keep a close eye on. Establishing processes to get QA as early as possible into architecture reviews, design reviews and other early processes that tend to only be dev, product, and design focused.
> Continue to build up our embedded QA unit to be sources of insight for multiple stakeholders and provide domain knowledge for our products. As QA we should always be asking two questions are we building the correct product? And are we building it correctly?