I look at whether the project is working seriously, not just listening to them talk about how grand the milestones are, but first checking how the treasury funds are spent: whether they are continuously paying for development, security audits, infrastructure—things that are "invisible but necessary"—or if they are just throwing money into the market, boosting exposure, holding conferences... The more "impressive" the money looks spent, the more guilty I feel. The same goes for milestones—frankly, don’t just give a PPT version of the roadmap; it’s best if it aligns with on-chain/repository/delivery rhythms: have the releases been made, are delays explained, has the budget been adjusted accordingly. Recently, modules and DA layer storytelling excite developers a lot, but users look confused. I actually want to see if they’ve explained costs, risks, and benefits in plain language. By the way: I see simplicity as a trap—hearing "we’ve got it done, it’ll be live soon" too often, I tend to ask a few more questions.