
I build and manage software products. Led product for agents @amplemarket, first PM @decipad.
Braga, Portugal
Joined November 2015
- Tweets612
- Following835
- Followers247
- Likes6.2K
João Pena retweeted
A massive thank you to everyone who attended Craftmatters 2025 and made it a day to remember! 💫
To the speakers who accepted our invitation and went on stage to share their wisdom and perspectives — we couldn’t be more grateful: @JooCamarate1, @joaompena, @HenrM_Cruz, @FabioMartins87, Marília Moita, @emanuelsa, @carvil_ , @dscape 👏
We left the room feeling inspired, challenged, and more connected to the craft than ever, and we hope you did too.
Craftmatters was a first for us, but definitely not the last. Until next time — let’s keep raising the bar, together. ✨
#Craftmatters2025
João Pena retweeted
What happens when you stop building features and start building intelligence into your product?
@joaompena, Senior Product Manager at @amplemarket, is helping reshape how modern go-to-market teams work by shipping AI-native products that don’t just assist users, but accelerate them. From prompt engineering to onboarding flows that write themselves, João brings a hybrid mindset rooted in product, design, and engineering. 🧠
At 𝐂𝐫𝐚𝐟𝐭𝐦𝐚𝐭𝐭𝐞𝐫𝐬 2025, he'll lead the masterclass “𝐈𝐧𝐬𝐢𝐝𝐞 𝐀𝐦𝐩𝐥𝐞𝐦𝐚𝐫𝐤𝐞𝐭 𝐃𝐮𝐨: 𝐁𝐮𝐢𝐥𝐝𝐢𝐧𝐠 𝐚 𝐏𝐢𝐨𝐧𝐞𝐞𝐫𝐢𝐧𝐠 𝐀𝐈‑𝐃𝐫𝐢𝐯𝐞𝐧 𝐏𝐫𝐨𝐝𝐮𝐜𝐭”.
If you’re building with (or around) AI and want to hear from someone in the trenches — this is your session.
📍 Join us at Craftmatters 2025 → bit.ly/Craftmatters_2025
🎟️ Tickets going fast!
João Pena retweeted
People talk about how AI is going to make design obsolete, and/or make pixel perfect designs not be a thing anymore. I don't think so.
Pixel-perfect design mostly existed in designers’ minds anyway. The mocks might perfect but the final product rarely was. Most of the time, those designs were shipped sloppily because the product organization didn’t have the patience to see the polish through. How many truly pixel-perfect products do you see out there?Especially with growth focused companies. There are exceptions, but not many.
The idea that AI might ruin visual quality feels like a non-issue since wasn’t much quality to ruin in the first place.
I also don't believe AI makes design obsolete but I believe it will raise the floor. That it’ll lift the skill level of product teams, and I hope it will free up time for the kind of polish that usually gets cut. So ideally we continue see more overall better design and the more "handcrafted" polished designs as well.
My general view of AI is that it will just let us do more things, not take away things. We didn't stop writing less when email was invented.
Few aspects:
1. AI as a skill multiplier. LLMs can elevate frontend and design quality for companies that historically couldn’t hire strong talent—or for individuals who haven’t built those muscles yet. In a way that way, it’s not that different from using UI kits, Tailwind, or shadcn.
2. Rethinking design systems. Design systems were a product of the ZIRP era, when teams scaled quickly and you couldn’t trust every person to design and build a decent button. So systems enforced quality through components and rules. But AI flip can this, and Instead of assembling rigid blocks, you can quickly build good scaffolding and refine with AI or by hand. LLMs might even enforce standards even better than design systems because they could be trained to spot inconsistencies and fix visual bugs automatically. The kinds of things that usually get deprioritized.
3. Designing closer to code.
I think AI will allow us to design more in code. I think it’s a good thing if we move away from pixel-perfect Figma files. The way I’ve always designed: Figma is where you design the vibe. Code is where you make it perfect. The real product is the one in production, not the mock. So that’s where polish should happen. Future design tools should make that process easier.
4. Taste still matters. For teams that already care about design, teams like @linear, none of this really changes the hard part. Achieving a polished UI is not that hard if you just have the practice. The hard part is conceptual. It’s figuring out how features fit together, how ideas map across the system. That’s where most of the iteration happens. That’s the part AI still can’t do for you.
So yes, AI will make things faster. It will increase the volume of output, but maybe it will also shift the baseline.
Holistic quality still depends on taste, systems thinking, and the willingness to care about the final experience.
João Pena retweeted
It's starting :)
xitter.cf/raycastapp/status/1894…
João Pena retweeted
Amplemarket is hiring!
Our next designer will have complete autonomy and will join the team currently revamping our brand and product, aiming to become a reference in the industry 🫡
read.cv/teams/amplemarket/se…
João Pena retweeted
People don’t want AI for AI’s sake. No one wants to chat with their expense report; they want their expense report to do itself.
When you need help, you won't have to read an FAQ, the product will show you how to use it (or just take the action for you) xitter.cf/tryramp/status/1792659…
João Pena retweeted
The first Founder Weekend by Founder Tales will be happening in Porto!
This is not just another hackathon. This is not just a bootcamp. It's a fully packed weekend where you can go from zero to solution, learn from the best, and even win some prizes!
More info in the link
João Pena retweeted
My article at Palladium Magazine examine's how the voting impossibility of structural reforms in Portugal's has led to a democracy that drives away its own while catering to immigrants, tourists, absentee landlords, and a growing retired population dependent on state benefits.
João Pena retweeted
Patrick Collison on the importance of beauty and craftsmanship when building products
“If Stripe is a monstrously successful business, but what we make isn’t beautiful, and Stripe doesn’t embody a culture of incredibly exacting craftsmanship, I’ll be much less happy. I think the returns to both of those things in the world are really high. I think even beyond the pecuniary or financial returns, the world’s just uglier than it needs to be… One can do things well or poorly, and beauty is not a rivalrous good.”
Patrick believes a commitment to craftsmanship and beauty played an important role in Stripe’s success:
“My intuition is that more of Stripe’s success than one would think is downstream of the fact that people like beautiful things—and for kind of rational reasons because what does a beautiful thing tell you? Well it tells you the person who made it really cared… And so if you care about the infrastructure being holistically good, indexing on the superficial characteristics that you can actually observe is not an irrational thing to do.”
João Pena retweeted
Replying to @karrisaarinen
I believe that we, as humans, will always tend to complicate what should be simple. I've found that when I'm in long loops about edge cases, this is probably the right time to reset and look at it from a different angle. Personally, I prefer to avoid errors, not design for them.
João Pena retweeted
2002 economic sciences laureate Daniel Kahneman has passed away aged 90.
He was awarded the prize for integrating insights from psychology into economics, especially human judgement and decision-making under uncertainty.
Learn about his life and work: bit.ly/2NTewKs
João Pena retweeted
Instead, you need to listen to that little voice that says "it's not quite right" for an uncomfortably long time.
João Pena retweeted
We’re announcing a new optimised model today! Mistral Large has top-tier reasoning capacities, is multi-lingual by design, has native function calling capacities and a 32k model. The pre-trained model has 81.2% accuracy on MMLU.
Learn more on mistral.ai/news/mistral-larg….
Mistral Large is available on la Plateforme, as well as on Azure, following our commitment to bring frontier AI everywhere. We're eager to see what developers do with Mistral Large!
João Pena retweeted
When we talk of beautiful products, we typically imagine attractive hardware or slick visuals -- the domain of designers or "creatives".
I think this is a gross misunderstanding.
When we compliment a database for being fast, or when we praise a concept for being easy to understand; when a marketing campaign stops us in our tracks or when scanning a dashboard gives us a sense of power, we are noticing the same sort of beauty.
It is the beauty that rages against the natural state of the world — inertia.
It is the beauty of the tremendous energy expended in taming disorder.
Is it the beauty of passion, the alchemy of turning work into purpose.
Do not judge a product’s beauty by its aesthetics; judge it by how it made you feel.
And do not be afraid to push for creating beautiful things.
João Pena retweeted
reinforcement learning from human feedback
Breaking: OpenAI board in discussions with Sam Altman to return as CEO trib.al/DTxl5tC
João Pena retweeted
I took a while to respond to this because Eric’s answers were very good, and logical so it’s hard to refute. I also do respect Eric Ries a lot, he has lot of experience with different companies and his book Lean Startup was really influential to me when it first came out.
But… something bothers me about this whole MVP discussion. Is this all just a distraction?
Eric’s answer was basically “MVP can be anything you need to validate an idea or the customer demand in the market”. Later in the discussion Eric mentions that a brochure can be an MVP. I agree. Sometimes sales material is a good way to validate demand, but I’d say it’s not an MVP. There is no product for anyone to use.
What bothers me is that if anything can be MVP, it’s trying to bucket all kinds of activities and outputs into this one term, it kind of loses in meaning and becomes more confusing than it’s helpful. Anything you do to validate an idea or build a product is essentially MVPs.
If MVP is just a way to test or validate something, then why not say, “I’m validating the product demand by using a sales brochure”. Or if I’m showing an initial product to potential users, why not just call it that. Why do I need to talk about MVPs? People also like to argue what truly is or not is an MVP, which I find just a waste of time.
In my experience, people generally mean MVP is some kind of baseline or beta version of a feature or product. It’s functional and hopefully solves user needs but doesn’t have all the polish and features. It’s a state in the product development lifecycle. Almost every product probably starts as some kind of “baseline” product where the baseline is defined by the expectations of the users. Which is fine, you have to start from somewhere.
The problem I’ve seen in companies is that this MVP thinking promotes taking constant shortcuts and shipping shitty things in the name of the MVP. These often get abandoned or not fixed afterwards because the project is technically done and the team moved over. Then the whole product becomes half-assed and disjointed because it’s just a string of MVPs.
Now someone might argue, well you are doing it wrong. MVPs doesn’t mean you shouldn’t finish it. Yes but in practice how often it happens and is this whole method just encouraging the wrong things or distracting from what are actually doing?
The MVPs & Lean Startups remind me of agile/scrum where you create these terms for a show or doing some mental gymnastics for basic activities. Then when someone argues it’s a waste of time the answer is often “you’re doing it wrong” or “you just don’t get it”. Maybe so, but maybe there isn’t anything to get?
My way of thinking around product building is not about experiments or MVPs, it’s about how to make the product successful.
As a startup you often just have to build something that people want. Providing a great experience is a great way to do that. Purposefully building and launching half-assed things to me is just a waste of time.
It’s like you operate a restaurant and instead of fully cooking the food, you purposefully leave it raw and let users tell you it’s inedible and makes them sick. Anyone who has eaten or cooked food knows that. Next time you cook it fully, and behold, the consumer now can eat the food but they still don't like it. Experiment and MVP of fully cooking the food was validated. Yay! We can now move to the next variable...
Obviously, chefs don't operate this way. They have their skills and experience and they use that make a dish and people would enjoy. Sometimes they are wrong and sometimes they make something really great.
Sometimes you know more about the market or the problem, sometimes you know less. You should try to think about what you do know, and what you don’t know, and how critical that information is. To know more you can talk to users and customers, knowing that they can’t ever give you the vision of what to build, only input to that vision. The ultimate test is to have a product out there, and see if people buy it. I’d say you should have vision, not just throw random stuff at people and see what they say.
This is also not about fear of launching a product early. We launch early and get feedback early, but still care about the quality of the experience. We got our first few users for @linear about 1 month after we announced the company. But by that time we already had a product that was 10x faster than anything else there, and had a design people liked. And yes it was scoped down and didn't have all the features (common sense). We never considered it as a MVP or an experiment, it was a product stage and we wanted to get user feedback.
My problem with trying to make the product building into some kind of science which most of the time is not necessarily and likely just a distraction, especially for startups. Your only focus should be how do I make a product that is 10x better than anything else in the market. The fact is that if you enter any category that only has solid incumbents or existing products, then your product needs to be very different and higher quality than those products. You don’t need an experiment to know that.
If your product has no traction then it either is the wrong product or the execution is not good enough. You can try to validate the product idea with research but until you make the execution good then you never know for sure. Users won't tell you that, they just leave or don't use it.
My point with this question was that today the user and customer expectations are high in many areas, and there are very few new novel markets like AI (crypto before that) that can be more of the wild west. But as those markets mature, you are again fighting against higher quality bars. As Bezos stated this, consumer expectations are ever increasing or “divinely discontent”,
So my advice would be to focus more on how you deliver a product that exceeds those expectations.
Don't spend your energy on running great experiments instead what would make the experience great.
Sidenote: On the iOS apps vs backup battery system also I disagree. Battery backup system buyers can have very high standards, but they are also rational buyers knowing what they want. Many consumer iOS apps only succeed in more irrational ways. There is no spec sheet for social apps you can pull out from teenagers. You can try to understand them and build something, but if it doesn’t engage them your app fails. These apps are not needed, they are wanted. Most products are some kind of mix of rational and irrational needs. Logic and emotion.
Replying to @karrisaarinen @ericries
@karrisaarinen got you an answer
See here for the full Q&A: youtu.be/xzebbzIntFc?si=ZQST…
























