-
@betsythemuffin It has, in many respects, been a lot of “preaching to the choir” when it comes to PE. In fact, mere mentions of the term often seem to close more doors than they open.
-
@betsythemuffin When working with folks on projects, I try to focus on the core features they need to consider the project successful. In eCommerce, it’s being able to check out. Then we start to examine how many potential barriers there are to that process.
-
@betsythemuffin Depending on the project/component/business that process can either go relatively smoothly or be incredibly tedious and painful (often, as you mention, involving a great many folks who aren’t involved in and don’t care about how it is technically achieved).
-
@betsythemuffin PE is a learning process for sure. It adds roughly 30% to a project’s scope & timeline for teams that aren’t used to the thought process (in my experience). That’s untenable to some companies (and probably most agencies/consultants).
-
@betsythemuffin That said, it does get easier over time. And once it’s integrated into your processes, it doesn’t add significantly to the process (again, in my experience).
-
@betsythemuffin But back to your original question (because it’s a good one)… I’d like to see more PE advocates work with frameworks to help them to come up with more resilient ways of building things. That can help us tackle one side of the equation (supply).
-
@betsythemuffin But we also need to work to educate the technical leaders and in-house customers of our web products. They need to understand the fragility of certain approaches so they ask for the right things which, in turn, puts pressure on devs to build more resilient products.
-
@betsythemuffin I think performance and accessibility are related ideas that are finally starting to gain a foothold in the tech leadership space. PE can naturally slip in there too.